Blockchain-based digital loan network

ABSTRACT

Systems and methods are provided for minting payment loan tokens to conduct digital loan transactions within a blockchain-based digital loan payment network. The payment loan tokens are pegged to fiat currency or digital currency. The computing system is a node in the blockchain-based digital loan payment network. A number of payment loan tokens to be provided to a borrower can be determined based on a digital loan transaction. The borrower is a network participant associated with the blockchain-based digital loan payment network. The number of payment loan tokens can be provided for deposit in a digital wallet associated with the borrower based on the digital loan transaction. Payees that receive payment loan tokens from the borrower can redeem the payment loan tokens as fiat or digital currency. A data record that represents the digital loan transaction can be generated. The data record is posted to a blockchain associated with the blockchain-based digital loan payment network.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit under 35 U.S.C. 119(e) of U.S.Provisional Application No. 63/133,098, filed on Dec. 31, 2020, thecontent of which is hereby incorporated in its entirety.

FIELD OF THE INVENTION

This disclosure relates to the use of blockchain technology to supportdigital loan and payment networks.

BACKGROUND

A blockchain network is generally comprised of nodes (e.g., computingsystems) that collaboratively manage a distributed database (e.g., adecentralized digital ledger). The decentralized digital ledger can beused to record various transactions that occur between networkparticipants in a verifiable manner. For example, nodes in a blockchainnetwork can record payment transactions in blocks that are successivelylinked together using cryptography to form a blockchain. Typically, eachblock in the blockchain includes a cryptographic hash of a precedingblock in the blockchain. The blockchain can continually be updated anddistributed to nodes in the blockchain network. In general, theblockchain improves transparency while ensuring data immutabilitysubject to consensus protocols.

SUMMARY

Various embodiments of the present disclosure can include systems,methods, and non-transitory computer readable media configured to mintpayment loan tokens to conduct digital loan transactions within ablockchain-based digital loan payment network. The payment loan tokensare pegged to fiat currency or digital currency. The computing system isa node in the blockchain-based digital loan payment network. A number ofpayment loan tokens to be provided to a borrower can be determined basedon a digital loan transaction. The borrower is a network participantassociated with the blockchain-based digital loan payment network. Thenumber of payment loan tokens can be provided for deposit in a digitalwallet associated with the borrower based on the digital loantransaction. Payees that receive payment loan tokens from the borrowercan redeem the payment loan tokens as fiat or digital currency. A datarecord that represents the digital loan transaction can be generated.The data record is posted to a blockchain associated with theblockchain-based digital loan payment network.

In an embodiment, the systems, methods, and non-transitory computerreadable media perform determining a request from a payee that receivedpayment loan tokens from the borrower to convert one or more paymentloan tokens to fiat or digital currency; providing instructions to acomputing system associated with a financial institution to convert theone or more payment loan tokens to fiat or digital currency; and causingthe one or more payment loan tokens to be burned.

In an embodiment, fiat currency or digital currency that is pegged tothe payment loan tokens is reduced based on the conversion of the one ormore payment loan tokens to fiat or digital currency.

In an embodiment, the systems, methods, and non-transitory computerreadable media perform determining a request from a payee that receivedpayment loan tokens from the borrower to convert one or more paymentloan tokens to fiat or digital currency; determining that a cash-outfunctionality associated with the payment loan tokens has been disabled;and providing a notification to the payee in response to the request,wherein the notification indicates that the request to convert the oneor more payment loan tokens to fiat or digital currency has been denied.

In an embodiment, determining that the cash-out functionality associatedwith the payment loan tokens has been disabled further includesdetermining that the borrower has defaulted on one or more loan paymentsassociated with the digital loan transaction.

In an embodiment, the cash-out functionality can be disabled to one ormore of: (i) prevent redemption of the payment loan tokens possessed bythe borrower, (ii) prevent redemption of payment loan tokens associatedwith the digital loan transaction that are in circulation within theblockchain-based digital loan payment network, or (iii) preventredemption of payment loan tokens associated with the digital loan thathave yet to be repaid.

In an embodiment, the payment loan tokens are loan-specific tokens thatare minted specifically for the digital loan transaction, the paymentloan tokens are lender-specific tokens that are minted specifically fora lender that processes the digital loan transaction, the payment loantokens are special purpose tokens that are minted specifically for aspecified special purpose, the payment loan tokens are industry-specifictokens that are minted specifically for transactions between entitiesassociated with a particular industry, the payment loan tokens aregeography-specific tokens that are minted specifically for transactionsbetween entities associated with a particular geographic region, thepayment loan tokens are country-specific tokens that are mintedspecifically for transactions between entities associated with aparticular country, the payment loan tokens are project-specific tokensthat are minted specifically for transactions between entitiesassociated with a particular project, or the payment loan tokens arelender-agnostic tokens that can be used to facilitate transactionsbetween entities regardless of lender.

In an embodiment, the systems, methods, and non-transitory computerreadable media perform generating a digital loan report based on one ormore queries to a blockchain associated with the blockchain-baseddigital loan payment network, wherein the digital loan report includestransaction information for the digital loan transaction recorded in theblockchain.

In an embodiment, the transaction information provides loan detailsincluding at least a principal amount associated with the digital loantransaction, an interest rate associated with the digital loantransaction, and a maturity date associated with the digital loantransaction.

In an embodiment, the blockchain-based digital loan payment networkcomprises a plurality of nodes including at least one minting nodeassociated with a lender that processes the digital loan transaction andat least one processing node associated with the lender.

In an embodiment, the systems, methods, and non-transitory computerreadable media perform determining that payment loan tokens associatedwith a digital wallet of a payee are inaccessible; determining a paymentloan token balance for the digital wallet based on the blockchainassociated with the blockchain-based digital loan payment network; andreplacing the payment loan tokens that are inaccessible with replacementpayment loan tokens.

In an embodiment, replacing the payment loan tokens that areinaccessible with replacement payment loan tokens includes burning thepayment loan tokens that are inaccessible; minting the replacementpayment loan tokens; and providing the replacement payment loan tokensto a replacement digital wallet associated with the payee.

In an embodiment, the systems, methods, and non-transitory computerreadable media perform determining a payment transaction between a firstpayee that received payment loan tokens from the borrower and a secondpayee; and generating a data record that represents the paymenttransaction, wherein the data record is posted to a blockchainassociated with the blockchain-based digital loan payment network.

In an embodiment, the systems, methods, and non-transitory computerreadable media perform determining a request from the second payee thatreceived payment loan tokens from the first payee to convert one or morepayment loan tokens to fiat or digital currency; providing instructionsto a computing system associated with a financial institution to convertthe one or more payment loan tokens to fiat or digital currency; andcausing the one or more payment loan tokens to be burned.

In an embodiment, a lender can define a smart contract to control usageof the payment loan tokens, wherein the smart contract canprogrammatically control usage of the payment loan tokens for at leastone of: a specified purpose, payee, or project.

Various embodiments of the present disclosure can include systems,methods, and non-transitory computer readable media configured todetermine a digital loan transaction between a lender and a borrowerassociated with a blockchain-based digital loan payment network. Thedigital loan transaction is based on payment loan tokens minted forcirculation in the blockchain-based digital loan payment network. A datarecord that represents the digital loan transaction between the lenderand the borrower associated with the blockchain-based digital loanpayment network is verified. The data record that represents the digitalloan transaction between the lender and the borrower associated with theblockchain-based digital loan payment network is posted in a blockchain.

In an embodiment, the blockchain records digital loan transactionsassociated with the blockchain-based digital loan payment network.

In an embodiment, the systems, methods, and non-transitory computerreadable media perform verifying a different data record that representsa different digital loan transaction between the lender and a differentborrower associated with the blockchain-based digital loan paymentnetwork, wherein the different digital loan transaction is based onpayment loan tokens minted for circulation in the blockchain-baseddigital loan payment network; and posting the different data record thatrepresents the different digital loan transaction between the lender andthe different borrower associated with the blockchain-based digital loanpayment network in the blockchain.

In an embodiment, the systems, methods, and non-transitory computerreadable media perform generating a digital loan report based on one ormore queries to the blockchain, wherein the digital loan report includestransaction information for the digital loan transaction recorded in theblockchain.

In an embodiment, the transaction information provides loan detailsincluding at least a principal amount associated with the digital loantransaction, an interest rate associated with the digital loantransaction, and a maturity date associated with the digital loantransaction.

In an embodiment, the systems, methods, and non-transitory computerreadable media perform verifying a different data record that representsa different digital loan transaction between a different lender and theborrower associated with a different blockchain-based digital loanpayment network, wherein the different digital loan transaction is basedon payment loan tokens minted for circulation in the differentblockchain-based digital loan payment network; and posting the differentdata record that represents the different digital loan transactionbetween the different lender and the borrower associated with thedifferent blockchain-based digital loan payment network in a differentblockchain associated with the different blockchain-based digital loanpayment network.

In an embodiment, the computing system is a node in a blockchain networkthat supports blockchain protocols for at least the blockchain-baseddigital loan payment network and the different blockchain-based digitalloan payment network.

In an embodiment, the systems, methods, and non-transitory computerreadable media perform generating a digital loan report based on one ormore queries to the blockchain associated with the differentblockchain-based digital loan payment network, wherein the digital loanreport includes transaction information for the different digital loantransaction recorded in the blockchain associated with the differentblockchain-based digital loan payment network.

In an embodiment, the lender is permitted to trace digital loantransactions that involve the payment loan tokens through theblockchain-based digital loan payment network.

In an embodiment, the blockchain-based digital loan payment networkcomprises a plurality of nodes including at least one minting nodeassociated with the lender, at least one first processing nodeassociated with the lender, and at least one second processing nodeassociated with a different lender.

These and other features of the systems, methods, and non-transitorycomputer readable media disclosed herein, as well as the methods ofoperation and functions of the related elements of structure and thecombination of parts and economies of manufacture, will become moreapparent upon consideration of the following description and theappended claims with reference to the accompanying drawings, all ofwhich form a part of this specification, wherein like reference numeralsdesignate corresponding parts in the various figures. It is to beexpressly understood, however, that the drawings are for purposes ofillustration and description only and are not intended as a definitionof the limits of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

Certain features of various embodiments of the present technology areset forth with particularity in the appended claims. A betterunderstanding of the features and advantages of the technology will beobtained by reference to the following detailed description that setsforth illustrative embodiments, in which the principles of the inventionare utilized, and the accompanying drawings of which:

FIG. 1A illustrates an example system for implementing blockchain-baseddigital loan payment networks, in accordance with various embodiments ofthe present technology.

FIG. 1B illustrates a flowchart of an example method, in accordance withvarious embodiments of the present technology.

FIG. 2A illustrates an example system for implementing a hostedblockchain-based digital loan payment network, in accordance withvarious embodiments of the present technology.

FIG. 2B illustrates another flowchart of an example method, inaccordance with various embodiments of the present technology.

FIG. 3 illustrates an example sequence diagram, in accordance withvarious embodiments of the present technology.

FIG. 4 illustrates an example computing system implementing an I-Nodemodule, in accordance with various embodiments of the presenttechnology.

FIG. 5 illustrates an example computing system implementing a T-Nodemodule, in accordance with various embodiments of the presenttechnology.

FIG. 6 illustrates an example computing system implementing a U-Nodemodule, in accordance with various embodiments of the presenttechnology.

FIGS. 7A-7E illustrate example diagrams, in accordance with variousembodiments of the present technology.

FIG. 8 illustrates a block diagram of an example computer system inwhich any of the embodiments described herein may be implemented.

DETAILED DESCRIPTION

A blockchain payment network is generally comprised of nodes (e.g.,computing systems) that collaboratively manage a distributed database(e.g., a decentralized digital ledger). The decentralized digital ledgercan be used to record various transactions that occur between networkparticipants in a verifiable manner. For example, nodes in a blockchainnetwork can record payment transactions in blocks that are successivelylinked together using cryptography to form a blockchain. Typically, eachblock in the blockchain includes a cryptographic hash of a precedingblock in the blockchain. The blockchain can continually be updated anddistributed to nodes in the blockchain network. In general, theblockchain improves transparency while ensuring data immutabilitysubject to consensus protocols.

Under conventional approaches, lenders (e.g., financial institutions)can loan money to borrowers (e.g., entities, individuals, companies,organizations, etc.) as fiat currency. For example, a financialinstitution can agree to loan a principal amount of money to a borrower.In this example, the borrower incurs a debt for the principal amount ofmoney and is typically obligated to repay the debt in addition tointerest by some maturity date. The loan can be recorded in a document,such as a promissory note, which can specify the principal amount ofmoney being borrowed, an interest rate being charged, the maturity date,among other details. The borrower can spend the loaned fiat currency asdesired without the financial institution's knowledge or control. Suchconventional approaches are associated with many disadvantages. Forexample, a financial institution that provides loans in fiat currencycan deplete its cash resources over time. For instance, loaned cashresources are typically recovered only after borrowers repay theirdebts. However, until debts are repaid, the financial institution losesits ability to allocate such cash resources to other investments.Another disadvantage with conventional approaches involves tracing andcontrol of loaned cash resources, if necessary. For example, underconventional approaches, a financial institution that loans fiatcurrency is typically unable to trace how a borrower spends the loanedfiat currency. As an example, a loan borrowed (or intended) for oneconstruction project can be used for another. Further, the financialinstitution typically has no control over the loaned fiat currency. Forinstance, the financial institution generally has no means to prevent orlimit losses when a borrower defaults.

A claimed solution rooted in computer technology overcomes problemsspecifically arising in the realm of computer technology. In variousembodiments, lenders (e.g., financial institutions, banks) can provideloans to borrowers through a blockchain-based digital loan paymentnetwork. For example, a financial institution can mint payment loantokens that can be used to conduct transactions within theblockchain-based digital loan payment network. The tokens can be peggedto fiat currency (e.g., U.S. dollars) that is deposited in an accountassociated with the financial institution. The amount of fiat currencyto which the tokens are pegged can be deposited in full or in part, forexample, based on a redeemable fiat currency requirement. In thisexample, the financial institution can provide loans based on its mintedtokens. These payment transactions can be recorded in a blockchainassociated with the digital loan payment network. The borrower caninitiate payments to payees based on tokens received from the financialinstitution as part of the loan. These payment transactions cansimilarly be recorded in the blockchain associated with the digital loanpayment network. The borrower and its payees can continue initiatingtoken-based payments to other payees as needed. For example, a payeethat received a token-based payment from the borrower can provide atoken-based payment to another payee. In various embodiments, payeeshave the option to redeem (or cash out) tokens. For example, a payeethat received a token-based payment can initiate an option to exchangethe tokens for fiat or digital currency from the loan issuing financialinstitution. In this example, the payee can transfer the tokens to adigital wallet associated with the financial institution in exchange forfiat or digital currency. Many variations are possible.

It can be especially advantageous for lenders to provide loans based oncryptocurrency tokens instead of fiat currency. For example, byproviding loans based on cryptocurrency tokens rather than fiatcurrency, the present technology allows a financial institution toretain access to its cash resources, which may be invested elsewhere. Asa result, the financial institution can earn interest on a digital loanfrom a borrower in addition to investment income from stayed cash. Ingeneral, the borrower can repay principal and interest in tokens, fiatcurrency, or digital currency. In the event the borrower repays theprincipal or interest in fiat currency, then the financial institutionbenefits by gaining access to additional cash resources that can beinvested elsewhere.

As another advantage, the present technology allows a lender toimplement smart contracts to programmatically control allocation andspending of loans, for example, based upon satisfaction of events orconditions or for specific project. As another advantage, the presenttechnology allows a lender to trace loaned tokens as they circulate fromborrowers to payees. For example, the lender can provide a token-basedloan to a borrower. The borrower can transfer some tokens to a firstpayee. The first payee can transfer some tokens to a second payee. Inthis example, the lender can trace the token payments from the lender tothe first payee and from the first payee to the second payee. As anotheradvantage, the present technology allows a lender to reduce its lossesfrom loan defaults. For example, if a borrower defaults on a token-basedloan, the lender has the option to prevent the borrower from redeemingany tokens associated with the loan for fiat currency. The lender canalso prevent any tokens associated with the loan that are in circulationfrom being redeemed. That is, the lender has the option to preventpayees of the borrower from redeeming tokens associated with the loanfor fiat currency. Further, the lender can also decide to preventredemption of only those tokens associated with the loan that have notbeen repaid by the borrower. As another advantage, the presenttechnology allows recovery of lost tokens associated with a digitalloan. As another advantage, the present technology helps reduce lenderrisk by increasing access to cash resources and limiting losses whenborrowers default. As a result, the present technology allows the lenderto provide a lower interest rate to borrowers. As yet another advantage,the present technology allows lenders to easily identify payees thatreceive token-based payments from borrowers. As a result, the presenttechnology allows lenders to engage those payees, for example, to pursuebanking relationships. More details describing the present technologyare provided below.

FIG. 1A illustrates a system 100 for implementing blockchain-baseddigital loan payment networks. The system 100 can include I-Nodes 102associated with a lender (“Financial Institution A”), T-Nodes 106associated with Financial Institution A, U-Nodes 108 associated withborrowers that have digital loans with Financial Institution A oranother lender (e.g., “Financial Institution B”), and U-Nodes 108associated with payees that can receive token-based payments from thoseborrowers. For example, an I-Node 102 can be implemented as an I-Nodemodule 404, as described in reference to FIG. 4 . A T-Node 106 can beimplemented as a T-Node module 504, as described in reference to FIG. 5. Further, a U-Node 108 can be implemented as a U-Node module 604, asdescribed in reference to FIG. 6 . In some embodiments, the I-Nodes 102,T-Nodes 106, and U-Nodes 108 can participate in a blockchain network120. In some embodiments, the I-Nodes 102 and T-Nodes 106 canparticipate in the blockchain network 120 as nodes while the U-Nodes 108participate as digital wallets. In some embodiments, a computing system104 associated with Financial Institution A can implement a digitalwallet that facilitates the transfer of monies from borrowers (e.g.,U-Nodes 108) to Financial Institution A. For example, the digital walletcan facilitate the transfer of fiat currency, tokens, or digitalcurrency from the borrower to Financial Institution A to digitallysubmit payments associated with a loan. In some embodiments, thecomputing system 104 associated with the Financial Institution A canalso implement a U-Node module 604, as described in reference to FIG. 6. Many variations are possible.

The blockchain network 120 can be associated with a blockchain based ona blockchain protocol. The blockchain can be used to record loantransactions that occur in a digital loan payment network associatedwith Financial Institution A. For example, the blockchain associatedwith the blockchain network 120 can be a “private” blockchain that isrestricted to Financial Institution A, borrowers that receivetoken-based loans from Financial Institution A, and payees that receivepayments from borrowers in tokens. In some embodiments, the I-Nodes 102can be configured to post blockchain transactions to the blockchainassociated with the blockchain network 120. In such embodiments, theT-Nodes 106 can be configured to validate transactions posted to theblockchain. In some embodiments, the both I-Nodes 102 and T-Nodes 106can be configured to post and validate blockchain transactions to theblockchain associated with the blockchain network 120. In general,transactions posted to the blockchain can be validated using generallyknown techniques including, for example, proof of work calculations andconfirmations, proof of stake calculations and confirmations, proof ofauthority calculations and confirmations, proof of history calculationsand confirmations, proof of two calculations and confirmations, andproof of N calculations and confirmations, to name some examples.

In various embodiments, the I-Nodes 102 and the T-Nodes 106 can beconfigured to manage a blockchain-based digital loan payment networkassociated with Financial Institution A. For example, the I-Nodes 102can be configured to mint and burn cryptocurrency tokens as needed tosupport the blockchain-based digital loan payment network. In someembodiments, the minted tokens are stablecoins pegged to a fiatcurrency. For example, a single token can be pegged to a single U.S.dollar. Thus, when minting tokens under such embodiments, FinancialInstitution A can cause some amount of fiat currency to be deposited,for example, in a bank (or escrow) account 105 associated with theFinancial Institution A. The amount deposited can be consistent with anamount of tokens to be minted. For example, Financial Institution A candeposit $100 to mint 100 tokens. However, Financial Institution A canalso deposit a lesser amount of fiat currency to mint the tokens. Forexample, Financial Institution A may only deposit an amount of fiatcurrency that is payable at any given time, such as $60 to mint 100tokens. Once deposited, the I-Nodes 102 can be instructed to minttokens. The I-Nodes 102 can also be instructed to transact withborrowers based on the minted tokens. For example, an I-Node 102 can beinstructed to initiate a digital loan payment of 1,000 tokens to aU-Node 108 associated with a borrower. The I-Nodes 102 can be configuredto mint different types of tokens depending on the implementation. Forexample, in an embodiment, the I-Nodes 102 can mint lender-specifictokens. That is, the I-Nodes 102 mint tokens that are specific toFinancial Institution A. In this embodiment, borrowers can use theminted tokens to repay any loans provided by Financial Institution A.Further, payees can exchange lender-specific tokens for fiat currencythrough Financial Institution A. In another embodiment, the I-Nodes 102can mint loan-specific tokens. That is, the I-Nodes 102 mint tokens thatare specific to a loan provided by Financial Institution A. In thisembodiment, a borrower that received the loan from Financial InstitutionA can use loan-specific tokens to repay the loan provided by FinancialInstitution A. Further, payees can exchange loan-specific tokens forfiat currency through Financial Institution A. In yet anotherembodiment, the I-Nodes 102 can mint universal tokens that are acceptedby Financial Institution A. In such embodiments, other lenders (e.g.,Financial Institution B) can also mint and accept the universal tokens.In this embodiment, borrowers can use universal tokens to repay anyloans provided by Financial Institution A or Financial Institution B.Further, payees can exchange universal tokens for fiat currency throughFinancial Institution A or Financial Institution B. Many variations arepossible. In some embodiments, the I-Nodes 102 can mint special purposetokens that facilitate transactions that relate to a specified purpose.In some embodiments, the I-Nodes 102 can mint industry-specific tokensthat facilitate transactions between entities associated with aparticular industry. In some embodiments, the I-Nodes 102 can mintgeographic-specific tokens that facilitate transactions between entitiesassociated with a particular geographic region. In some embodiments, theI-Nodes 102 can mint country-specific tokens that facilitatetransactions between entities associated with a particular country. Insome embodiments, the I-Nodes 102 can mint project-specific tokens thatfacilitate transactions between entities associated with a particularproject. In some embodiments, the I-Nodes 102 can mint lender-agnostictokens that can be used to facilitate transactions between entitiesregardless of lender.

The I-Nodes 102 can be configured to generate data records reflectingloan transactions. A data record can correspond to a blockchaintransaction to be posted to the blockchain associated with theblockchain network 120. The data record may include various detailsdescribing the transaction, such a transaction description (e.g.,transaction date, sender address, destination address, transactionamount), payment purpose, recipient, project, entity information (e.g.,entity name, wallet address, etc.), loan details (e.g., principalamount, interest rate, maturity date, etc.), among other information.The data record may then be posted to the blockchain. For example, thedata record may be posted by the I-Node 102. The data record may besubsequently verified by one or more nodes included in the blockchainnetwork 120, such as the T-Nodes 106. The data record may then be a partof the blockchain associated with the blockchain network 120.

A borrower that accepts a digital loan from Financial Institution A canconduct transactions with other entities based on tokens in itspossession. For example, the borrower can pay 80 tokens to a U-Node 108associated with a first payee. Similarly, the first payee can pay 50tokens to a U-Node 108 associated with a second payee. In variousembodiments, payees can convert tokens to fiat (or digital) currencythrough the blockchain network 120. For example, the first payee caninteract with the I-Nodes 102 and/or the computing system 104 associatedwith Financial Institution A to exchange the remaining 30 tokens forfiat currency, e.g., 30 USD. In this example, the first payee cantransfer the 30 tokens to a digital wallet associated with FinancialInstitution A, such as the computing system 104. The computing system104 can then be instructed to transfer 30 USD from the bank account 105to a bank account associated with the first payee. Once transferred, theexchanged tokens can be burned (or cryptographically destroyed).Similarly, the second payee can interact with the I-Nodes 102 and/or thecomputing system 104 associated with Financial Institution A to exchangethe 50 tokens for fiat currency, e.g., 50 USD. Additionally, in variousembodiments, the borrower can make payments associated with a loan, suchas principal and interest, through the blockchain network 120. Forexample, the borrower can pay the principal or interest in tokens, fiatcurrency, or digital currency.

The system 100 can include I-Nodes 122 associated with FinancialInstitution B, T-Nodes 126 associated with Financial Institution B,U-Nodes 108 associated with borrowers that have loans with FinancialInstitution A or Financial Institution B, and U-Nodes 108 associatedwith payees that can receive token-based payments from those borrowers.For example, an I-Node 122 can be implemented as an I-Node module 404,as described in reference to FIG. 4 . A T-Node 126 can be implemented asa T-Node module 504, as described in reference to FIG. 5 . Further, aU-Node 108 can be implemented as a U-Node module 604, as described inreference to FIG. 6 . In some embodiments, the I-Nodes 122, T-Nodes 126,and U-Nodes 108 can participate in a blockchain network 130. In someembodiments, the I-Nodes 122 and T-Nodes 126 can participate in theblockchain network 130 as nodes while the U-Nodes 108 participate asdigital wallets. In some embodiments, a computing system 124 associatedwith Financial Institution B can implement a digital wallet thatfacilitates the transfer of monies from borrowers (e.g., U-Nodes 108) toFinancial Institution B. For example, the digital wallet can facilitatethe transfer of fiat currency, tokens, or digital currency from theborrower to Financial Institution B to digitally submit paymentsassociated with a loan. In some embodiments, the computing system 124associated with the Financial Institution B can also implement a U-Nodemodule 604, as described in reference to FIG. 6 . Many variations arepossible. In some instances, payees may be associated with multipleblockchain-based digital loan payment networks. In such instances, aU-Node associated with the payee can be associated with multipleblockchain networks. For example, in FIG. 1A, a U-Node 112 controlled bya payee can be included in both the blockchain-based digital loanpayment network associated with Financial Institution A (e.g., theblockchain network 120) and the blockchain-based digital loan paymentnetwork associated with Financial Institution B (e.g., the blockchainnetwork 130). In this example, the U-Node 112 can be configured toimplement blockchain protocols utilized by both the blockchain network120 and the blockchain network 130. Many variations are possible.

The blockchain network 130 can be associated with a blockchain based ona blockchain protocol. The blockchain can be used to record loantransactions that occur in a digital loan payment network associatedwith Financial Institution B. For example, the blockchain associatedwith the blockchain network 130 can be a “private” blockchain that isrestricted to Financial Institution B, borrowers that receivetoken-based loans from Financial Institution B, and payees that receivepayment from borrowers in tokens. In some embodiments, the I-Nodes 122can be configured to post blockchain transactions to the blockchainassociated with the blockchain network 130. In such embodiments, theT-Nodes 126 can be configured to validate transactions posted to theblockchain. In some embodiments, the both I-Nodes 122 and T-Nodes 126can be configured to post and validate blockchain transactions to theblockchain associated with the blockchain network 130. In general,transactions posted to the blockchain can be validated using generallyknown techniques including, for example, proof of work calculations andconfirmations, proof of stake calculations and confirmations, proof ofauthority calculations and confirmations, proof of history calculationsand confirmations, proof of two calculations and confirmations, andproof of N calculations and confirmations, to name some examples.

The I-Nodes 122 and the T-Nodes 126 can be configured to manage theblockchain-based digital loan payment network associated with FinancialInstitution B. For example, the I-Nodes 122 can be configured to mintand burn cryptocurrency tokens as needed to support the blockchain-baseddigital loan payment network, as described above. The I-Nodes 122 canalso be instructed to transact with borrowers based on the mintedtokens.

The I-Nodes 122 can be configured to generate data records reflectingloan transactions. A data record can correspond to a blockchaintransaction to be posted to the blockchain associated with theblockchain network 130. The data record may include various detailsdescribing the transaction, such a transaction description (e.g.,transaction date, sender address, destination address, transactionamount,), entity information (e.g., entity name, wallet address, etc.),loan details (e.g., principal amount, interest rate, maturity date,etc.), payment purpose, recipient, project, among other information. Thedata record may then be posted to the blockchain. For example, the datarecord may be posted by the I-Node 122. The data record may besubsequently verified by one or more nodes included in the blockchainnetwork 130, such as the T-Nodes 126. The data record may then be a partof the blockchain associated with the blockchain network 130.

A borrower that accepts a loan from Financial Institution B can conducttransactions with other entities based on tokens in its possession. Forexample, the borrower can pay 160 tokens to a U-Node 108 associated witha first payee. Similarly, the first payee can pay 100 tokens to a U-Node108 associated with a second payee. In various embodiments, payees canconvert tokens to fiat (or digital) currency through the blockchainnetwork 130. For example, the first payee can interact with the I-Nodes122 and/or the computing system 124 associated with FinancialInstitution B to exchange the remaining 60 tokens for fiat currency. Inthis example, the first payee can transfer the 60 tokens to a digitalwallet associated with Financial Institution B, such as the computingsystem 124. The computing system 124 can then be instructed to transfera corresponding amount of fiat currency (e.g., 60 USD) from the bankaccount 125 to a bank account associated with the first payee. Oncetransferred, the exchanged tokens can be burned (or cryptographicallydestroyed). Similarly, the second payee can interact with the I-Nodes122 and/or the computing system 124 associated with FinancialInstitution B to exchange the 100 tokens for fiat currency.Additionally, in various embodiments, the borrower can make paymentsassociated with a loan, such as principal and interest, through theblockchain network 130.

FIG. 1B illustrates a flowchart of an example method 150, according tovarious embodiments of the present disclosure. For example, the method150 can be performed by the system 100 of FIG. 1A.

At block 152, payment loan tokens to conduct digital loan transactionswithin a blockchain-based digital loan payment network are minted by acomputing system. The payment loan tokens are pegged to fiat currency ordigital currency. The computing system is a node in the blockchain-baseddigital loan payment network. At block 154, a number of payment loantokens to be provided to a borrower can be determined based on a digitalloan transaction. The borrower is a network participant associated withthe blockchain-based digital loan payment network. At block 156, thenumber of payment loan tokens can be provided for deposit in a digitalwallet associated with the borrower based on the digital loantransaction. Payees that receive payment loan tokens from the borrowercan redeem the payment loan tokens as fiat or digital currency. At block158, a data record that represents the digital loan transaction can begenerated. The data record is posted to a blockchain associated with theblockchain-based digital loan payment network.

The operations of method 150 are intended to be illustrative. Dependingon the implementation, the example method 150 may include additional,fewer, or alternative steps performed in various orders or in parallel.The example method 150 may be implemented in various computing systemsor devices including one or more processors.

FIG. 2A illustrates a system 200 for implementing a blockchain-baseddigital loan payment network. The system 200 can include I-Nodes 202associated with a lender (“Financial Institution A”), I-Nodes 222associated with another lender (“Financial Institution B”), T-Nodes 206associated with a consortium (e.g., banking consortium), U-Nodes 208associated with borrowers that have digital loans with lenders (e.g.,Financial Institution A, Financial Institution B, etc.), and U-Nodes 208associated with payees that can receive token-based payments fromborrowers. In some embodiments, each lender associated with the bankingconsortium can contribute and manage one or more T-Nodes 206. Forexample, Financial Institution A can manage a T-Node 214 and FinancialInstitution B can manage a T-Node 216. In another embodiment, theT-Nodes 206 can be hosted by a third-party service provider. In variousembodiments, I-Nodes 202 and I-Nodes 222 can be implemented as I-Nodemodules 404, as described in reference to FIG. 4 . A T-Node 206 can beimplemented as a T-Node module 504, as described in reference to FIG. 5. Further, a U-Node 208 can be implemented as a U-Node module 604, asdescribed in reference to FIG. 6 . In some embodiments, the I-Nodes 202,I-Nodes 222, T-Nodes 206, and U-Nodes 208 can participate in ablockchain network 220. In some embodiments, the I-Nodes 202, I-Nodes222, and T-Nodes 206 can participate in the blockchain network 220 asnodes while the U-Nodes 208 participate as digital wallets. Manyvariations are possible.

In some embodiments, a computing system 204 associated with FinancialInstitution A can implement a digital wallet that facilitates thetransfer of monies from borrowers (e.g., U-Nodes 208) to FinancialInstitution A. For example, the computing system 204 can facilitatedigital transfers of fiat currency, tokens, or digital currency from aborrower to Financial Institution A, for example, to submit paymentsassociated with a loan. The computing system 204 can also facilitateconversion of payment loan tokens to fiat or digital currency. In someembodiments, the computing system 204 associated with the FinancialInstitution A can also implement a U-Node module 604, as described inreference to FIG. 6 . Similarly, a computing system 224 associated withFinancial Institution B can implement a digital wallet that facilitatesthe transfer of monies from borrowers (e.g., U-Nodes 208) to FinancialInstitution B. For example, the computing system 224 can facilitatedigital transfers of fiat currency, tokens, or digital currency from aborrower to Financial Institution B, for example, to submit paymentsassociated with a loan. The computing system 224 can also facilitateconversion of payment loan tokens to fiat or digital currency. In someembodiments, the computing system 224 associated with the FinancialInstitution B can also implement a U-Node module 604, as described inreference to FIG. 6 .

The blockchain network 220 can be associated with a blockchain. Invarious embodiments, the blockchain can be used to record transactionsthat involve various tokens circulated in different blockchain-baseddigital loan payment networks. That is, the blockchain supportstransactions based on different types of payment loan tokens. Forexample, in FIG. 2A, the blockchain can be used to record transactionsthat occur in digital loan payment networks associated with bothFinancial Institution A and Financial Institution B. For example, theblockchain can support transactions that involve payments based on atleast payment loan tokens minted by Financial Institution A (e.g., theI-Nodes 202) and transactions that involve payments based on paymentloan tokens minted by Financial Institution B (e.g., the I-Nodes 222).In some embodiments, the blockchain associated with the blockchainnetwork 220 can be a “private” blockchain that is restricted to lenders(e.g., Financial Institution A, Financial Institution B), borrowers, andpayees. In some embodiments, the blockchain associated with theblockchain network 220 can be hosted by a third-party service provider.In some embodiments, the I-Nodes 202, I-Nodes 222, and T-Nodes 206 canbe configured to post blockchain transactions to the blockchainassociated with the blockchain network 220. The I-Nodes 202, I-Nodes222, and T-Nodes 206 can also be configured to validate transactionsposted to the blockchain. In some embodiments, only T-Nodes 206 can beconfigured to post transactions to the blockchain associated with theblockchain network 220 and validate transactions posted to theblockchain. In general, transactions posted to the blockchain can bevalidated using generally known techniques including, for example, proofof work calculations and confirmations, proof of stake calculations andconfirmations, proof of authority calculations and confirmations, proofof history calculations and confirmations, proof of two calculations andconfirmations, and proof of N calculations and confirmations, to namesome examples.

The I-Nodes 202 can be configured to manage a blockchain-based digitalloan payment network for Financial Institution A. For example, theI-Nodes 202 can be configured to mint and burn payment loan tokens asneeded to support the blockchain-based digital loan payment network. Insome embodiments, the minted tokens are stable coins pegged to a fiat ordigital currency. For example, a single token can be pegged to a singleU.S. dollar. Thus, when minting tokens under such embodiments, FinancialInstitution A can cause some amount of fiat currency to be deposited ina bank account 205, for example, through the computing system 204associated with Financial Institution A. The amount deposited can beconsistent with or less than an amount of tokens to be minted. Oncedeposited, the I-Nodes 202 can be instructed to mint tokens commensurateto the amount of fiat currency deposited or payable loan amount. TheI-Nodes 202 can also be instructed to transact with loan borrowers basedon the minted tokens. The I-Nodes 202 can be configured to generate adata record reflecting each loan transaction. The data record cancorrespond to a blockchain transaction to be posted to the blockchainassociated with the blockchain network 220. The data record may includevarious details describing the transaction, such a transactiondescription (e.g., transaction date, sender address, destinationaddress, transaction amount), entity information (e.g., entity name,wallet address, etc.), loan details (e.g., principal amount, interestrate, maturity date, etc.), payment purpose, recipient, project, amongother information. The data record may then be posted to the blockchain.For example, the data record may be posted by the I-Node 202. The datarecord may be subsequently verified by one or more nodes included in theblockchain network 220, such as the T-Nodes 206. The data record maythen be a part of the blockchain associated with the blockchain network220. For example, an I-Node 202 can be instructed to provide digitalloan payments based on minted tokens to borrowers. Borrowers cantransact with payees based on the minted tokens. Borrowers can also usethe minted tokes to repay a loan principal or interest to FinancialInstitution A. Further, payees can redeem (or exchange) tokens receivedto fiat or digital currency through Financial Institution A.

The I-Nodes 202 can be configured to mint different types of tokensdepending on the implementation. For example, in an embodiment, theI-Nodes 202 can mint lender-specific tokens. That is, the I-Nodes 202mint tokens that are specific to Financial Institution A. In thisembodiment, borrowers can use the minted tokens to repay any loansprovided by Financial Institution A. Further, payees can exchangelender-specific tokens for fiat currency through Financial InstitutionA. In another embodiment, the I-Nodes 202 can mint loan-specific tokens.That is, the I-Nodes 202 mint tokens that are specific to a loanprovided by Financial Institution A. In this embodiment, a borrower thatreceived the loan from Financial Institution A can use loan-specifictokens to repay the loan provided by Financial Institution A. Further,payees can exchange loan-specific tokens for fiat currency throughFinancial Institution A. In yet another embodiment, the I-Nodes 202 canmint universal tokens that are accepted by Financial Institution A. Insuch embodiments, other lenders (e.g., Financial Institution B) can alsomint and accept the universal tokens. In this embodiment, borrowers canuse universal tokens to repay any loans provided by FinancialInstitution A or Financial Institution B. Further, payees can exchangeuniversal tokens for fiat currency through Financial Institution A orFinancial Institution B. Many variations are possible. In someembodiments, the I-Nodes 202 can mint special purpose tokens thatfacilitate transactions that relate to a specified purpose. In someembodiments, the I-Nodes 202 can mint industry-specific tokens thatfacilitate transactions between entities associated with a particularindustry. In some embodiments, the I-Nodes 202 can mintgeographic-specific tokens that facilitate transactions between entitiesassociated with a particular geographic region. In some embodiments, theI-Nodes 202 can mint country-specific tokens that facilitatetransactions between entities associated with a particular country. Insome embodiments, the I-Nodes 202 can mint project-specific tokens thatfacilitate transactions between entities associated with a particularproject. In some embodiments, the I-Nodes 202 can mint lender-agnostictokens that can be used to facilitate transactions between entitiesregardless of lender.

For example, when minting tokens under such embodiments, FinancialInstitution A can cause some amount of fiat currency to be deposited inthe bank (or escrow) account 205. The amount deposited can be consistentwith or less than an amount of tokens to be minted. For example,Financial Institution A can deposit $100 to mint 100 tokens. In anotherexample, Financial Institution A can deposit $50 to mint 100 tokens.Once deposited, the I-Nodes 202 can be instructed to mint tokenscommensurate to the amount of fiat currency deposited or payable loanamount. The I-Nodes 202 can also be instructed to transact with loanborrowers based on the minted tokens. For example, an I-Node 202 can beinstructed to initiate a payment of 1,000 tokens to a borrower. TheI-Node 202 can be configured to generate a data record reflecting theloan transaction. The data record can correspond to a blockchaintransaction to be posted to the blockchain associated with theblockchain network 220. The data record may include various detailsdescribing the transaction, such as a transaction description (e.g.,transaction date, sender address, destination address, transactionamount), entity information (e.g., entity name, wallet address, etc.),loan details (e.g., principal amount, interest rate, maturity date,etc.), payment purpose, recipient, project, among other information. Thedata record may then be posted to the blockchain. For example, the datarecord may be posted and verified by one or more nodes included in theblockchain network 220, such as the T-Nodes 206. The data record maythen be a part of the blockchain associated with the blockchain network220. The borrower can conduct transactions with other entities based ontokens available to the borrower. For example, the borrower can pay 20tokens to a network participant that corresponds to a payee. As oneexample, the borrower can pay Company A for an invoice in payment loantokens. Company A has the option to convert the payment loan tokensreceived from the borrower to fiat or digital currency. In this example,Company A can interact with the I-Nodes 202 and/or the computing system204 associated with Financial Institution A to exchange the tokens forfiat currency. The exchanged tokens can be burned (or cryptographicallydestroyed).

Similarly, the I-Nodes 222 can be configured to manage ablockchain-based digital loan payment network for Financial InstitutionB. For example, the I-Nodes 222 can be configured to mint and burnpayment loan tokens as needed to support the blockchain-based digitalloan payment network. In some embodiments, the minted tokens are stablecoins pegged to a fiat or digital currency. For example, a single tokencan be pegged to a single U.S. dollar. Thus, when minting tokens undersuch embodiments, Financial Institution B can cause some amount of fiatcurrency to be deposited in a bank (or escrow) account 225, for example,through the computing system 224 associated with Financial InstitutionB. The amount deposited can be consistent with or less than an amount oftokens to be minted. Once deposited, the I-Nodes 222 can be instructedto mint tokens commensurate to the amount of fiat currency deposited orpayable loan amount. The I-Nodes 222 can also be instructed to transactwith loan borrowers based on the minted tokens. The I-Nodes 222 can beconfigured to generate a data record reflecting each loan transaction.The data record can correspond to a blockchain transaction to be postedto the blockchain associated with the blockchain network 220. The datarecord may include various details describing the transaction, such atransaction description (e.g., transaction date, sender address,destination address, transaction amount), entity information (e.g.,entity name, wallet address, etc.), loan details (e.g., principalamount, interest rate, maturity date, etc.), payment purpose, recipient,project, among other information. The data record may then be posted tothe blockchain. For example, the data record may be posted by the I-Node222. The data record may be subsequently verified by one or more nodesincluded in the blockchain network 220, such as the T-Nodes 206. Thedata record may then be a part of the blockchain associated with theblockchain network 220. For example, an I-Node 222 can be instructed toprovide digital loan payments based on minted tokens to borrowers.Borrowers can transact with payees based on the minted tokens. Borrowerscan also use the minted tokes to repay a loan principal or interest toFinancial Institution B. Further, payees can redeem (or exchange) tokensreceived to fiat or digital currency through Financial Institution B.

The I-Nodes 222 can be configured to mint different types of tokensdepending on the implementation. For example, in an embodiment, theI-Nodes 222 can mint lender-specific tokens. That is, the I-Nodes 222mint tokens that are specific to Financial Institution B. In thisembodiment, borrowers can use the minted tokens to repay any loansprovided by Financial Institution B. Further, payees can exchangelender-specific tokens for fiat currency through Financial InstitutionB. In another embodiment, the I-Nodes 222 can mint loan-specific tokens.That is, the I-Nodes 222 mint tokens that are specific to a loanprovided by Financial Institution B. In this embodiment, a borrower thatreceived the loan from Financial Institution B can use loan-specifictokens to repay the loan provided by Financial Institution B. Further,payees can exchange loan-specific tokens for fiat currency throughFinancial Institution B. In yet another embodiment, the I-Nodes 222 canmint universal tokens that are accepted by Financial Institution B. Insuch embodiments, other lenders (e.g., Financial Institution A) can alsomint and accept the universal tokens. In this embodiment, borrowers canuse universal tokens to repay any loans provided by FinancialInstitution B or Financial Institution A. Further, payees can exchangeuniversal tokens for fiat currency through Financial Institution B orFinancial Institution A. Many variations are possible. In someembodiments, the I-Nodes 102 can mint special purpose tokens thatfacilitate transactions that relate to a specified purpose. In someembodiments, the I-Nodes 102 can mint industry-specific tokens thatfacilitate transactions between entities associated with a particularindustry. In some embodiments, the I-Nodes 102 can mintgeographic-specific tokens that facilitate transactions between entitiesassociated with a particular geographic region. In some embodiments, theI-Nodes 102 can mint country-specific tokens that facilitatetransactions between entities associated with a particular country. Insome embodiments, the I-Nodes 102 can mint project-specific tokens thatfacilitate transactions between entities associated with a particularproject. In some embodiments, the I-Nodes 102 can mint lender-agnostictokens that can be used to facilitate transactions between entitiesregardless of lender.

For example, when minting tokens under such embodiments, FinancialInstitution B can cause some amount of fiat currency to be deposited inthe bank account 225. The amount deposited can be consistent with orless than an amount of tokens to be minted. For example, FinancialInstitution B can deposit $100 to mint 100 tokens. In another example,Financial Institution B can deposit $50 to mint 100 tokens. Oncedeposited, the I-Nodes 222 can be instructed to mint tokens commensurateto the amount of fiat currency deposited or payable loan amount. TheI-Nodes 222 can also be instructed to transact with loan borrowers basedon the minted tokens. For example, an I-Node 222 can be instructed toinitiate a payment of 1,000 tokens to a borrower. The I-Node 222 can beconfigured to generate a data record reflecting the loan transaction.The data record can correspond to a blockchain transaction to be postedto the blockchain associated with the blockchain network 220. The datarecord may include various details describing the transaction, such atransaction description (e.g., transaction date, sender address,destination address, transaction amount), entity information (e.g.,entity name, wallet address, etc.), loan details (e.g., principalamount, interest rate, maturity date, etc.), payment purpose, recipient,project, among other information. The data record may then be posted tothe blockchain. For example, the data record may be posted and verifiedby one or more nodes included in the blockchain network 220, such as theT-Nodes 206. The data record may then be a part of the blockchainassociated with the blockchain network 220. The borrower can conducttransactions with other entities based on tokens available to theborrower. For example, the borrower can pay 20 tokens to a networkparticipant that corresponds to a payee. As one example, the borrowercan pay Company A for an invoice in payment loan tokens. Company A hasthe option to convert the payment loan tokens received from the borrowerto fiat or digital currency. In this example, Company A can interactwith the I-Nodes 222 and/or the computing system 224 associated withFinancial Institution B to exchange the tokens for fiat currency. Theexchanged tokens can be burned (or cryptographically destroyed).

FIG. 2B illustrates a flowchart of an example method 250, according tovarious embodiments of the present disclosure. For example, the method250 can be performed by the system 200 of FIG. 2A.

At block 252, a determination is made of a digital loan transactionbetween a lender and a borrower associated with a blockchain-baseddigital loan payment network. The digital loan transaction is based onpayment loan tokens minted for circulation in the blockchain-baseddigital loan payment network. At block 254, a data record thatrepresents the digital loan transaction between the lender and theborrower associated with the blockchain-based digital loan paymentnetwork is verified. At block 256, the data record that represents thedigital loan transaction between the lender and the borrower associatedwith the blockchain-based digital loan payment network is posted in ablockchain.

The operations of method 250 are intended to be illustrative. Dependingon the implementation, the example method 250 may include additional,fewer, or alternative steps performed in various orders or in parallel.The example method 250 may be implemented in various computing systemsor devices including one or more processors.

FIG. 3 illustrates an example sequence diagram 300, in accordance withvarious embodiments of the present technology. The example sequencediagram 300 illustrates an example set of interactions (or transactions)between a lender 302, borrower 304, Payee A 306, and Payee B 308 througha blockchain-based digital loan payment network in accordance withvarious embodiments of the present technology. It should be appreciatedthat there can be additional, fewer, or alternative steps performed insimilar or alternative orders, or in parallel, within the scope of thevarious embodiments unless otherwise stated.

For example, the lender 302 can mint cryptocurrency (or payment loantokens) that can be used to conduct transactions within theblockchain-based digital loan payment network. The tokens can be peggedto fiat or digital currency that is deposited partially or fully in anaccount (e.g., bank account, escrow account, etc.) associated with thelender 302. The lender 302 can mint payment loan tokens based on thedeposited fiat currency or loan amount. At step 312, the lender 302 canprovide a digital loan token to the borrower 304. The digital loantransaction can be recorded in a blockchain associated with theblockchain-based digital loan payment network, as described herein. Atstep 314, the borrower 304 makes a payment to Payee A 306 in the amountof 100 tokens. At step 316, Payee A 306 makes a payment to Payee B 308in the amount of 80 tokens. At step 318, Payee A 306 redeems 20 tokensin exchange for fiat or digital currency. For example, the lender 302can receive the 20 tokens and in response provide Payee A 306 with fiator digital currency based on the redeemed 20 tokens. The fiat or digitalcurrency can be withdrawn from the escrow account associated with thelender 302. At step 320, Payee B 308 redeems 30 tokens in exchange forfiat or digital currency. For example, the lender 302 can receive the 30tokens and in response provide Payee B 308 with fiat or digital currencybased on the redeemed 30 tokens. The fiat or digital currency can bewithdrawn from the escrow account associated with the lender 302. Atstep 322, the borrower 304 can make a loan payment to the lender 302.For example, the borrower 304 can repay its loan principal or interestassociated with the loan. In various embodiments, the borrower 304 canmake the loan payment using tokens, fiat currency, and/or digitalcurrency. In general, when tokens are redeemed, the lender 302 canredeem out of the escrow account or a different account if the escrowaccount has insufficient funds.

In various embodiments, the lender 302 can trace transactions thatinvolve tokens provided as a loan to the borrower 304. In the example ofFIG. 3 , the lender 302 can access transaction details associated withtokens paid to Payee A at step 314. The transaction details can identifyPayee A as a payee and an amount of tokens provided to Payee A.Similarly, the lender 302 can access transaction details associated withtokens paid to Payee B at step 316. The transaction details can identifyPayee B as a payee and an amount of tokens provided to Payee B. Manyvariations are possible.

FIG. 4 illustrates an example environment 400, in accordance withvarious embodiments. The example environment 400 can include at least acomputing system 402. The computing system 402 can include one or moreprocessors and memory among other components, as described in referenceto FIG. 8 . The processors can be configured to perform variousoperations by interpreting machine-readable instructions. The computingsystem 402 can include an I-Node module 404. The I-Node module 404 caninclude a blockchain module 406, a token manager module 408, a walletmodule 410, and an application module 412. The blockchain module 406,token manager module 408, wallet module 410, and application module 412can be executed by the processor(s) of the computing system 402 toperform various operations, as described below. In some embodiments, theI-Node module 404 can be implemented, in whole or in part, as softwarethat is capable of running on one or more computing systems or devices.In some embodiments, the I-Node module 404 can be implemented, in wholeor in part, as software that is capable of running on one or moreservers (e.g., cloud servers). In some embodiments, the I-Node module404 can be implemented, in whole or in part, as software that is capableof running on one or more virtual machines.

The computing system 402 can access a data store 430. In general, a datastore may be any device in which data can be stored and from which datacan be retrieved. In some embodiments, the data store 430 may store andmanage various data, such as blockchain data, information describingblockchain protocols, encryption keys and algorithms, communicationprotocols and standards, data formatting standards and protocols,program code for modules and application programs of the processingdevice, and other data that may be suitable for use by the I-Node module404 to perform the functions disclosed herein. The computing system 402can access the data store 430 either directly or over a computernetwork. The computer network may be any wired or wireless networkthrough which data can be sent and received (e.g., the internet, localarea network, etc.).

The I-Node module 404 can interact with the computing system 402 to sendand receive data over one or more networks based on one or more networkprotocols. For example, the I-Node module 404 can be configured toexchange data (e.g., receive data, send data) with other I-Nodes,T-Nodes, U-Nodes, financial institutions, blockchain networks, and otherentities over computer networks, such as the internet. The I-Node module404 can also be configured to exchange (e.g., send, receive) blockchaindata, for example, with other I-Nodes, T-Nodes, and blockchain networks.The blockchain data may comprise a blockchain and associated datarecords included in the blockchain. For example, a blockchain datarecord can describe a blockchain transaction between networkparticipants. The data record can include information, such as atransaction description (e.g., transaction date, sender address,destination address, transaction amount), entity information (e.g.,entity name, wallet address, etc.), loan details (e.g., principalamount, interest rate, maturity date, etc.), payment purpose, recipient,project, among other information, such as smart contracts associatedwith the blockchain transaction. The I-Node module 404 can store suchblockchain data in the data store 430.

The blockchain module 406 can be configured to manage one or moreblockchains based on various blockchain protocols. In general, theblockchain module 406 can implement generally known blockchainprotocols. A blockchain protocol can define a set of rules for managinga blockchain associated with a blockchain network. For example, theblockchain module 406 can implement a blockchain protocol thatfacilitates transactions based on cryptocurrency (e.g., tokens, coins,stablecoins). The blockchain may be configured to store a plurality ofdata records using a suitable data storage format and schema. Theblockchain may be formatted based on generally known approaches. Forexample, the blockchain can be stored as a relational database thatutilizes structured query language to process structured data setsstored therein. Each data record stored in the blockchain can beassociated with a transaction and include blockchain data associatedtherewith, such as a transaction description (e.g., transaction date,sender address, destination address, transaction amount), entityinformation (e.g., entity name, wallet address, etc.), loan details(e.g., principal amount, interest rate, maturity date, etc.), paymentpurpose, recipient, project, among other information as known to personshaving skill in the relevant art. As an example, the blockchain can beused to record transactions relating to digital loans provided by someentity, such as a financial institution. In such embodiments, theblockchain can be managed based on a blockchain protocol associated withthe financial institution. Further, the transactions can be based oncryptocurrency that is managed (e.g., minted, burned) by the financialinstitution. In other embodiments, digital loan transactions involvingvarious entities (or financial institutions) can be based on a universalblockchain protocol. Further, the transactions can be based oncryptocurrency that is managed (e.g., minted, burned) by a hostedblockchain network platform or a banking consortium, for example.

The blockchain module 406 can be configured to query a blockchain. Forexample, the blockchain module 406 can query a blockchain fortransaction details based on terms associated with a search query. Forexample, the blockchain module 406 can execute queries to retrieve (oridentify) blockchain data representing various transactions based onvarious search criteria. In some embodiments, the blockchain module 406can restrict which entities are permitted to submit such queries. Forexample, in some embodiments, only a lender associated with ablockchain-based digital loan payment network is permitted to query theblockchain for transactions involving tokens loaned by the lender. Manyvariations are possible.

The blockchain module 406 can be configured to generate data records tobe stored in a blockchain based on a blockchain protocol. The datarecord may be a data record suitable for inclusion in the blockchain andinclude data suitable for use in validation of a given transaction. Theincluded data may comprise transaction data values. In some embodiments,one or more of the transaction data values included in the generateddata record may be hashed and/or encrypted using one or more suitablehashing and encryption algorithms, respectively.

The blockchain module 406 can update a blockchain based on generateddata records. For example, the blockchain module 406 can determine thata new transaction has occurred. In this example, the blockchain module406 can execute a query to update the blockchain to add a data recordassociated with the new transaction. In some instances, the blockchainmay be stored locally, such as a blockchain stored in the data store430. In other instances, the blockchain may be associated with ablockchain network. In such instances, when the blockchain is updatedwith a generated data record, the generated data record can be submittedto the blockchain network and/or one or more nodes associated with theblockchain network for validation and/or posting to the blockchain. Insome embodiments, the blockchain module 406 can provide (or broadcast) anotification, for example, to other modules of the I-Node module 404 ornodes in the blockchain network, once the blockchain is updated.

The blockchain module 406 can be configured to verify (or validate) datarecords to be stored in a blockchain. For example, the blockchain module406 may receive a data record to be added to a blockchain. The datarecord can describe a transaction. The blockchain module 406 may beconfigured to validate the data record using one or more suitablemethods, such as a proof of work method associated with thecorresponding blockchain including, for example, proof of stakecalculations and confirmations, proof of authority calculations andconfirmations, proof of history calculations and confirmations, proof oftwo calculations and confirmations, and proof of N calculations andconfirmations, to name some examples. The blockchain module 406 can alsooutput an indication of success or failure for the validation. Forexample, if the validation of the data record is successful, theblockchain module 406 may indicate that validation of the data recordwas completed successfully. As a result, the data record can be added tothe blockchain and propagated or broadcasted to nodes of a correspondingblockchain network. The blockchain module 406 can also send anotification to the corresponding blockchain network and/or one or morenodes in the corresponding blockchain network to indicate the successfulvalidation of the data record. Many variations are possible.

The blockchain module 406 can be configured to electronically transmitdata to a blockchain network for posting new blockchain transactions toa blockchain. In some embodiments, the blockchain module 406 canelectronically transmit data to different blockchain networks. In suchembodiments, the blockchain module 406 can identify a blockchain networkto which data is to be transmitted based on a network identifierassociated with the blockchain network as provided in blockchain data(e.g., data records). In some embodiments, the blockchain module 406 canalso be configured to transmit validation data to the blockchain networkand to nodes associated with the blockchain network. For example, thevalidation data can be transmitted for data records newly added to theblockchain associated with the blockchain network.

The token manager module 408 can be configured to manage payment loantokens that can be used to conduct transactions. For example, the tokenmanager module 408 can be configured to exchange fiat or digitalcurrency for cryptocurrency tokens, minting new tokens as needed, andburning previously used tokens as necessary. In some embodiments, tokensminted by the token manager module 408 are pegged to a fiat currency(e.g., U.S. dollars). As an example, a single token can be pegged to asingle U.S. dollar. In such embodiments, an entity (e.g., a financialinstitution) that controls a computing node implementing the I-Nodemodule 404 can allocate fiat or digital currency (e.g., US Dollars) inan amount consistent with or less than an amount of tokens to be minted.The minted tokens can be stored in a digital wallet and be used by theentity to provide digital loans based on the minted tokens. The fiat ordigital currency can be stored in an account (e.g., bank account, escrowaccount) associated with the financial institution. In some embodiments,the financial institution can process requests to redeem (e.g.,exchange, cash out) tokens from entities that received a digital loantoken from the financial institution. For example, a computing systemassociated with the financial institution can process requests to redeemtokens from payees of a borrower.

The token manager module 408 can be configured to mint different typesof tokens depending on the implementation. For example, in anembodiment, the token manager module 408 can mint lender-specifictokens. That is, the token manager module 408 mint tokens that arespecific to a financial institution (e.g., Financial Institution A,Financial Institution B, etc.). In this embodiment, borrowers can usethe minted tokens to repay any loans provided by the financialinstitution. Further, payees can exchange lender-specific tokens forfiat currency through the financial institution. In another embodiment,the token manager module 408 can mint loan-specific tokens. That is, thetoken manager module 408 mint tokens that are specific to a loanprovided by a financial institution. In this embodiment, a borrower thatreceived the loan from the financial institution can use loan-specifictokens to repay the loan provided by the financial institution. Further,payees can exchange loan-specific tokens for fiat currency through thefinancial institution. In yet another embodiment, the token managermodule 408 can mint universal tokens that are accepted by the financialinstitution. In such embodiments, other lenders can also mint and acceptthe universal tokens. In this embodiment, borrowers can use universaltokens to repay any loans regardless of lender. Further, payees canexchange universal tokens for fiat currency through any lender. Manyvariations are possible. In some embodiments, the token manager module408 can mint special purpose tokens that facilitate transactions thatrelate to a specified purpose. In some embodiments, the token managermodule 408 can mint industry-specific tokens that facilitatetransactions between entities associated with a particular industry. Insome embodiments, the token manager module 408 can mintgeographic-specific tokens that facilitate transactions between entitiesassociated with a particular geographic region. In some embodiments, thetoken manager module 408 can mint country-specific tokens thatfacilitate transactions between entities associated with a particularcountry. In some embodiments, the token manager module 408 can mintproject-specific tokens that facilitate transactions between entitiesassociated with a particular project. In some embodiments, the tokenmanager module 408 can mint lender-agnostic tokens that can be used tofacilitate transactions between entities regardless of lender.

The wallet module 410 can be configured to manage one or more digitalwallets associated with a given entity (e.g., a financial institution).The digital wallets can be implemented using generally known approachesfor storing and managing payment loan tokens. For example, in variousembodiments, the wallet module 410 can provide options to send tokens toparticipants in a blockchain network and receive tokens fromparticipants in the blockchain network. In some embodiments, the walletmodule 410 provides an option to redeem (or cash out) tokens stored in adigital wallet for fiat or digital currency. For example, a networkparticipant can interact with the wallet module 410 to request that someamount of tokens be converted to fiat or digital currency. In thisexample, the wallet module 410 can determine an amount of fiat ordigital currency to be withdrawn from an account at a financialinstitution based on the amount of tokens to be converted. The walletmodule 410 can provide a request to withdraw the amount of fiat ordigital currency from the account to a computing system associated withthe financial institution. The computing system associated with thefinancial institution can provide an electronic payment to the networkparticipant in response to the request to withdraw. The converted tokenscan be burned as part of the withdrawal. In some embodiments, the walletmodule 410 can be implemented as a software application that can run oncomputing devices.

The application module 412 can be configured to apply blockchain datafor various applications. For example, in some embodiments, theapplication module 412 can create and evaluate smart contracts based ongenerally known approaches. A smart contract can involve transactionsinvolving multiple entities in a blockchain network. The applicationmodule 412 can provide various options to construct and evaluate smartcontracts. For example, a smart contract can be written as computer codethat is committed to a blockchain. The smart contract can be associatedwith conditions. When an event described in the smart contract istriggered, the computer code associated with the smart contract canexecute. As an example, a smart contract may be created between afinancial institution and a borrower. The smart contract can beassociated with a condition that requires the borrower to electronicallysign for a digital loan before the financial institution provides tokensto a digital wallet associated with the borrower. Many variations arepossible. In various embodiments, a smart contract can be programmed toprocess digital loan tokens when one or more conditions are satisfied.For example, a smart contract can be associated with a condition thatrequires use of digital loan tokens for a specified purpose. In anotherexample, a smart contract can be associated with a condition thatrequires use of digital loan tokens for a specified project. In yetanother example, a smart contract can be associated with a conditionthat requires use of digital loan tokens for a specified payee.

The application module 412 can be configured to generate a digital loanreport. For example, the application module 412 can query a blockchainto identify digital loan transactions. The identified transactions canbe used to generate a report that identifies various transactioninformation, such as transaction descriptions (e.g., transaction date,sender address, destination address, transaction amount), loan details(e.g., principal amount, interest rate, maturity date, etc.), and entityinformation (e.g., entity name, wallet address, etc.), payment purpose,recipient, project, for example. The report can thus identify paymentsmade from one entity to another entity. For example, the report canidentify digital loan details processed by a financial institution for aborrower. In another example, the report can identify digital paymentsfrom the borrower to payees. In yet another example, the report canidentify digital loan payments from the borrower to the financialinstitution, such as payments towards loan interest and/or principal. Insuch embodiments, the financial institution can readily identify digitalloan borrowers and payees based on transactions conducted by thoseborrowers and payees based on payment loan tokens.

The application module 412 can be configured to trace payments involvingtokens associated with a given digital loan. For example, theapplication module 412 can trace tokens associated with a digital loanmade to a borrower and payments involving those tokens from the borrowerto payees. In some embodiments, the application module 412 can query ablockchain to identify transactions associated with a given digitalloan. The identified transactions can be analyzed to trace circulationof tokens associated with the digital loan in a blockchain network. Insome embodiments, the application module 412 can trace tokens based on adigital loan report, as described above.

The application module 412 can be configured to disable tokenredemption. For example, a lender can provide a borrower with tokensassociated with a digital loan. The borrower can use the tokens to payothers. In some instances, the borrower may default on loan obligations.For instance, the borrower may fail to make a loan payment. In suchinstances, the application module 412 can be configured to limit thelender's losses by preventing entities from cashing out tokensassociated with the digital loan. The application module 412 can also beconfigured to limit the lender's losses by preventing entities frommaking payments to payees. In some embodiments, the application module412 can disable all tokens associated with the digital loan that are inthe borrower's possession. Other approaches are possible. For example,in some embodiments, the application module 412 can disable all tokensassociated with the digital loan that are in circulation regardless ofwhich entity possesses the tokens. In some embodiments, the applicationmodule 412 can only disable tokens associated with the digital loan thathave not been repaid.

The application module 412 can be configured to recover lost (e.g.,misplaced, deleted, inaccessible, etc.) loan tokens. For example, whenan entity loses access to a digital wallet, a blockchain that managestransactions involving the loan tokens can be queried to determine atoken balance associated with the digital wallet and informationdescribing the lost loan tokens. The lost loan tokens can be identifiedbased on the queried information. The lost loan tokens can automaticallybe transferred to a lender that provided the lost loan tokens. Thelender can burn the lost loan tokens. The application module 412 canthen facilitate minting replacement tokens and transferring thereplacement tokens to a replacement digital wallet associated with theentity. Many variations are possible.

FIG. 5 illustrates an example environment 500, in accordance withvarious embodiments. The example environment 500 can include at least acomputing system 502. The computing system 502 can include one or moreprocessors and memory among other components, as described in referenceto FIG. 8 . The processors can be configured to perform variousoperations by interpreting machine-readable instructions. The computingsystem 502 can include a T-Node module 504. The T-Node module 504 caninclude a blockchain module 506, a wallet module 508, and an applicationmodule 510. The blockchain module 506, wallet module 508, andapplication module 510 can be executed by the processor(s) of thecomputing system 502 to perform various operations, as described below.In some embodiments, the T-Node module 504 can be implemented, in wholeor in part, as software that is capable of running on one or morecomputing systems or devices. In some embodiments, the T-Node module 504can be implemented, in whole or in part, as software that is capable ofrunning on one or more servers (e.g., cloud servers). In someembodiments, the T-Node module 504 can be implemented, in whole or inpart, as software that is capable of running on one or more virtualmachines.

The computing system 502 can access a data store 530. In general, a datastore may be any device in which data can be stored and from which datacan be retrieved. In some embodiments, the data store 530 may store andmanage various data, such as blockchain data, information describingblockchain protocols, encryption keys and algorithms, communicationprotocols and standards, data formatting standards and protocols,program code for modules and application programs of the processingdevice, and other data that may be suitable for use by the T-Node module504 to perform the functions disclosed herein. The computing system 502can access the data store 530 either directly or over a computernetwork. The computer network may be any wired or wireless networkthrough which data can be sent and received (e.g., the Internet, localarea network, etc.).

The T-Node module 504 can interact with the computing system 502 to sendand receive data over one or more networks based on one or more networkprotocols. For example, the T-Node module 504 can be configured toexchange data (e.g., receive data, send data) with other I-Nodes,T-Nodes, U-Nodes, financial institutions, blockchain networks, and otherentities over computer networks, such as the Internet. The T-Node module504 can also be configured to exchange (e.g., send, receive) blockchaindata, for example, with other I-Nodes, T-Nodes, and blockchain networks.The blockchain data may comprise a blockchain and associated datarecords included in the blockchain. For example, a blockchain datarecord can describe a blockchain transaction between networkparticipants. The data record can include information, such as atransaction description (e.g., transaction date, sender address,destination address, transaction amount), entity information (e.g.,entity name, wallet address, etc.), loan details (e.g., principalamount, interest rate, maturity date, etc.), payment purpose, recipient,project, among other information, such as smart contracts associatedwith the blockchain transaction. The T-Node module 504 can store suchblockchain data in the data store 530.

The blockchain module 506 can be configured to manage one or moreblockchains based on various blockchain protocols. In general, theblockchain module 506 can implement generally known blockchainprotocols. A blockchain protocol can define a set of rules for managinga blockchain associated with a blockchain network. For example, theblockchain module 506 can implement a blockchain protocol thatfacilitates transactions based on cryptocurrency (e.g., tokens, coins,stablecoins). The blockchain may be configured to store a plurality ofdata records using a suitable data storage format and schema. Theblockchain may be formatted based on generally known approaches. Forexample, the blockchain can be stored as a relational database thatutilizes structured query language to process structured data setsstored therein. Each data record stored in the blockchain can beassociated with a transaction and include blockchain data associatedtherewith, such as a transaction description (e.g., transaction date,sender address, destination address, transaction amount), entityinformation (e.g., entity name, wallet address, etc.), loan details(e.g., principal amount, interest rate, maturity date, etc.), paymentpurpose, recipient, project, among other information as known to personshaving skill in the relevant art. As an example, the blockchain can beused to record transactions relating to digital loans provided by someentity, such as a financial institution. In such embodiments, theblockchain can be managed based on a blockchain protocol associated withthe financial institution. Further, the transactions can be based oncryptocurrency that is managed (e.g., minted, burned) by the financialinstitution. Many variations are possible. In various embodiments, theblockchain module 506 can support different blockchains for differentlenders. For example, the blockchain module 506 can manage a firstblockchain that records digital loan transactions associated with afirst lender and a second blockchain that records digital loantransactions associated with a second lender.

The blockchain module 506 can be configured to query a blockchain. Forexample, the blockchain module 406 can query a blockchain fortransaction details based on terms associated with a search query. Forexample, the blockchain module 506 can execute queries to retrieve (oridentify) blockchain data representing various transactions based onvarious search criteria. In some embodiments, the blockchain module 506can restrict which entities are permitted to submit such queries. Forexample, in some embodiments, only a lender associated with ablockchain-based digital loan payment network is permitted to query theblockchain for transactions involving tokens loaned by the lender. Manyvariations are possible.

The blockchain module 506 can be configured to generate data records tobe stored in a blockchain based on a blockchain protocol. The datarecord may be a data record suitable for inclusion in the blockchain andinclude data suitable for use in validation of a given transaction. Theincluded data may comprise transaction data values. In some embodiments,one or more of the transaction data values included in the generateddata record may be hashed and/or encrypted using one or more suitablehashing and encryption algorithms, respectively.

The blockchain module 506 can update a blockchain based on generateddata records. For example, the blockchain module 506 can determine thata new transaction has occurred. In this example, the blockchain module506 can execute a query to update the blockchain to add a data recordassociated with the new transaction. In some instances, the blockchainmay be stored locally, such as a blockchain stored in the data store530. In other instances, the blockchain may be associated with ablockchain network. In such instances, when the blockchain is updatedwith a generated data record, the generated data record can be submittedto the blockchain network and/or one or more nodes associated with theblockchain network for validation and posting to the blockchain. In someembodiments, the blockchain module 506 can provide (or broadcast) anotification, for example, to other modules of the T-Node module 504 ornodes in the blockchain network, once the blockchain is updated.

The blockchain module 506 can be configured to verify (or validate) datarecords to be stored in a blockchain. For example, the blockchain module506 may receive a data record to be added to a blockchain. The datarecord can describe a transaction. The blockchain module 506 may beconfigured to validate the data record using one or more suitablemethods, such as a proof of work method associated with thecorresponding blockchain including, for example, proof of stakecalculations and confirmations, proof of authority calculations andconfirmations, proof of history calculations and confirmations, proof oftwo calculations and confirmations, and proof of N calculations andconfirmations, to name some examples. The blockchain module 506 can alsooutput an indication of success or failure for the validation. Forexample, if the validation of the data record is successful, theblockchain module 506 may indicate that validation of the data recordwas completed successfully. As a result, the data record can be added tothe blockchain and propagated or broadcasted to nodes of a correspondingblockchain network. The blockchain module 506 can also send anotification to the corresponding blockchain network and/or one or morenodes in the corresponding blockchain network to indicate the successfulvalidation of the data record. Many variations are possible.

The blockchain module 506 can be configured to electronically transmitdata to a blockchain network for posting new blockchain transactions tothe blockchain. In some embodiments, the blockchain module 506 canelectronically transmit data to different blockchain networks. In suchembodiments, the blockchain module 506 can identify a blockchain networkto which data is to be transmitted based on a network identifierassociated with the blockchain network as provided in blockchain data(e.g., data records). In some embodiments, the blockchain module 506 canalso be configured to transmit validation data to the blockchain networkand to nodes associated with the blockchain network. For example, thevalidation data can be transmitted for data records newly added to theblockchain associated with the blockchain network.

In some embodiments, the blockchain module 506 can be configured tomanage a unified blockchain associated with a blockchain network. Theblockchain can be used to record transactions that occur in differentblockchain-based digital loan payment networks. That is, the blockchainsupports transactions based on different types of payment loan tokensthat are minted for circulation in different blockchain-based digitalloan payment networks. For example, the blockchain can be used to recordtransactions that occur in a first blockchain-based digital loan paymentnetwork associated with Financial Institution A and a secondblockchain-based digital loan payment network associated with FinancialInstitution B. For example, the blockchain can support transactions thatinvolve payments based on payment loan tokens minted by FinancialInstitution A (e.g., the I-Nodes 202) and transactions that involvepayments based on payment loan tokens minted by Financial Institution B(e.g., the I-Nodes 222). In some embodiments, the blockchain associatedwith the blockchain network can be a “private” blockchain that isrestricted to Financial Institution A and/or Financial Institution B,including borrowers and payees. In some embodiments, the nodes of theblockchain network can be configured to post blockchain transactions tothe blockchain. The nodes can also be configured to validatetransactions posted to the blockchain. In general, transactions postedto the blockchain can be validated using generally known techniquesincluding, for example, proof of work calculations and confirmations,proof of stake calculations and confirmations, proof of authoritycalculations and confirmations, proof of history calculations andconfirmations, proof of two calculations and confirmations, and proof ofN calculations and confirmations, to name some examples. In someembodiments, the blockchain is hosted by a blockchain-based digital loannetwork. In such embodiments, the blockchain can be managed exclusivelyby the blockchain-based digital loan network. For example, in suchembodiments, the T-Node module 504 can be implemented in one or morecomputer nodes that are managed by the blockchain-based digital loannetwork.

The wallet module 508 can be configured to manage one or more digitalwallets associated with a given entity (e.g., financial institution).The digital wallets can be implemented using generally known approachesfor storing and managing payment loan tokens. For example, in variousembodiments, the wallet module 508 can provide options to send tokens toparticipants in a blockchain network and receive tokens fromparticipants in the blockchain network. In some embodiments, the walletmodule 508 provides an option to redeem (or cash out) tokens stored in adigital wallet for fiat or digital currency. For example, a networkparticipant can interact with the wallet module 508 to request that someamount of tokens be converted to fiat or digital currency. In thisexample, the wallet module 508 can determine an amount of fiat ordigital currency to be withdrawn from an account at a financialinstitution based on the amount of tokens to be converted. The walletmodule 508 can provide a request to withdraw the amount of fiat ordigital currency from the account to a computing system associated withthe financial institution. The computing system associated with thefinancial institution can provide an electronic payment to the networkparticipant in response to the request to withdraw. The converted tokenscan be burned as part of the withdrawal. In some embodiments, the walletmodule 508 can be implemented as a software application that can run oncomputing devices. Many variations are possible. In some embodiments,the wallet module 508 can be implemented as a software application thatcan run on computing servers. In some embodiments, the wallet module 508can implement a multi-token digital wallet that is capable of managingcryptocurrency tokens associated with different blockchain-based digitalloan payment networks.

The application module 510 can be configured to use blockchain data forvarious applications. For example, in some embodiments, the applicationmodule 510 can create and evaluate smart contracts based on generallyknown approaches. A smart contract can involve transactions involvingmultiple entities in a blockchain network. The application module 510can provide various options to construct and evaluate smart contracts.For example, a smart contract can be written as computer code that iscommitted to a blockchain. The smart contract can be associated withconditions. When an event described in the smart contract is triggered,the computer code associated with the smart contract can execute. As anexample, a smart contract may be created between a financial institutionand a borrower. The smart contract can be associated with a conditionthat requires the borrower to electronically sign for a digital loanbefore the financial institution provides tokens to a digital walletassociated with the borrower. Many variations are possible. In variousembodiments, a smart contract can be programmed to process digital loantokens when one or more conditions are satisfied. For example, a smartcontract can be associated with a condition that requires use of digitalloan tokens for a specified purpose. In another example, a smartcontract can be associated with a condition that requires use of digitalloan tokens for a specified project. In yet another example, a smartcontract can be associated with a condition that requires use of digitalloan tokens for a specified payee.

The application module 510 can be configured to generate a digital loanreport. For example, the application module 510 can query a blockchainto identify digital loan transactions. The identified transactions canbe used to generate a report that identifies various transactioninformation, such as transaction descriptions (e.g., transaction date,sender address, destination address, transaction amount), loan details(e.g., principal amount, interest rate, maturity date, etc.), and entityinformation (e.g., entity name, wallet address, etc.), payment purpose,recipient, project, for example. The report can thus identify paymentsmade from one entity to another entity. For example, the report canidentify digital loan details processed by a financial institution for aborrower. In another example, the report can identify digital paymentsfrom the borrower to payees. In yet another example, the report canidentify digital loan payments from the borrower to the financialinstitution, such as payments towards loan interest and/or principal. Insuch embodiments, the financial institution can readily identify digitalloan borrowers and payees based on transactions conducted by thoseborrowers and payees based on payment loan tokens.

FIG. 6 illustrates an example environment 600, in accordance withvarious embodiments. The example environment 600 can include at least acomputing system 602. The computing system 602 can include one or moreprocessors and memory among other components, as described in referenceto FIG. 8 . The processors can be configured to perform variousoperations by interpreting machine-readable instructions. The computingsystem 602 can include a U-Node module 604. The U-Node module 604 caninclude a wallet module 606 and an application module 608. The walletmodule 606 and application module 608 can be executed by theprocessor(s) of the computing system 602 to perform various operations,as described below. In some embodiments, the U-Node module 604 can beimplemented, in whole or in part, as software that is capable of runningon one or more computing systems or devices. In some embodiments, theU-Node module 604 can be implemented, in whole or in part, as softwarethat is capable of running on one or more servers (e.g., cloud servers).

The computing system 602 can access a data store 630. In general, a datastore may be any device in which data can be stored and from which datacan be retrieved. In some embodiments, the data store 630 may store andmanage various data, such as blockchain data, information describingblockchain protocols, encryption keys and algorithms, communicationprotocols and standards, data formatting standards and protocols,program code for modules and application programs of the processingdevice, and other data that may be suitable for use by the U-Node module604 to perform the functions disclosed herein. The computing system 602can access the data store 630 either directly or over a computernetwork. The computer network may be any wired or wireless networkthrough which data can be sent and received (e.g., the Internet, localarea network, etc.).

The U-Node module 604 can interact with the computing system 602 toreceive data over one or more networks based on one or more networkprotocols. For example, the U-Node module 604 can be configured toexchange data (e.g., receive data, send data) with other I-Nodes,T-Nodes, U-Nodes, financial institutions, blockchain networks, and otherentities over computer networks, such as the internet. The U-Node module604 can also be configured to receive blockchain data, for example, fromother I-Nodes, T-Nodes, and blockchain networks. The blockchain data maycomprise a blockchain and associated data records included in theblockchain. For example, a blockchain data record can describe ablockchain transaction between network participants. The data record caninclude information, such a transaction description (e.g., transactiondate, sender address, destination address, transaction amount), entityinformation (e.g., entity name, wallet address, etc.), loan details(e.g., principal amount, interest rate, maturity date, etc.), paymentpurpose, recipient, project, among other information, such as smartcontracts associated with the blockchain transaction. The U-Node module604 can store such blockchain data in the data store 630.

The wallet module 606 can be configured to manage one or more digitalwallets associated with an entity (e.g., a network participant). Thedigital wallets can be implemented using generally known approaches forstoring and managing cryptocurrency and payment loan tokens. Forexample, in various embodiments, the wallet module 606 can provideoptions to send tokens to other entities in a blockchain network andreceive tokens from other entities in the blockchain network. In someembodiments, the wallet module 606 provides an option to redeem (or cashout) tokens stored in a digital wallet for fiat or digital currency. Forexample, an entity can interact with the wallet module 606 to requestthat some amount of tokens be converted to fiat or digital currency. Inthis example, the wallet module 606 can determine an amount of fiat ordigital currency to be withdrawn from an account at a financialinstitution based on the amount of tokens to be converted. The walletmodule 606 can provide a request to withdraw the amount of fiat ordigital currency from the account to a computing system associated withthe financial institution. The computing system associated with thefinancial institution can provide an electronic payment to the networkparticipant in response to the request to withdraw. The converted tokenscan be burned as part of the withdrawal. Many variations are possible.In some embodiments, the wallet module 606 can be implemented as asoftware application that can run on computing devices. In someembodiments, the wallet module 606 can implement a multi-token digitalwallet that is capable of managing cryptocurrency tokens associated withdifferent blockchain-based digital loan payment networks.

The application module 608 can be configured to use blockchain data forvarious applications. For example, in some embodiments, the applicationmodule 608 can create and evaluate smart contracts based on generallyknown approaches. A smart contract can involve transactions involvingmultiple entities in a blockchain network. The application module 608can provide various options to construct and evaluate smart contracts.For example, a smart contract can be written as computer code that iscommitted to a blockchain. The smart contract can be associated withconditions. When an event described in the smart contract is triggered,the computer code associated with the smart contract can execute. Invarious embodiments, a smart contract can be programmed to processdigital loan tokens when one or more conditions are satisfied. Forexample, a smart contract can be associated with a condition thatrequires use of digital loan tokens for a specified purpose. In anotherexample, a smart contract can be associated with a condition thatrequires use of digital loan tokens for a specified project. In yetanother example, a smart contract can be associated with a conditionthat requires use of digital loan tokens for a specified payee.

FIG. 7A illustrates an example sequence diagram 700, in accordance withvarious embodiments of the present technology. The example sequencediagram 700 illustrates an example set of interactions (or transactions)between a lender 702, borrower 704, and payee 706 through ablockchain-based digital loan payment network in accordance with variousembodiments of the present technology. It should be appreciated thatthere can be additional, fewer, or alternative steps performed insimilar or alternative orders, or in parallel, within the scope of thevarious embodiments unless otherwise stated.

For example, the lender 702 can mint cryptocurrency (or payment loantokens) that can be used to conduct transactions within theblockchain-based digital loan payment network. The tokens can be peggedto fiat or digital currency that is deposited partially or fully in anaccount associated with the lender 702. The lender 702 can mint paymentloan tokens based on the deposited fiat currency or loan amount. At step710, the lender 702 can provide a digital loan to the borrower 704. Thedigital loan transaction can be recorded in a blockchain associated withthe blockchain-based digital loan payment network, as described herein.At step 712, the borrower 704 makes a payment to payee 706 in the amountof 50 tokens. At step 714, the borrower 704 defaults on a loan paymentto the lender 702 in accordance with the digital loan. As a result, thelender 702 can disable its cashing-out functionality in an effort tolimit its losses from the default. For example, at step 716, the payee706 attempts to exchange 50 tokens for fiat currency through the lender702. At step 718, the lender 702 can deny the exchange request and canprovide a response to the payee 706 indicating that cashing-outfunctionality is disabled. Many variations are possible.

FIG. 7B illustrates a diagram of an example blockchain 720. The exampleblockchain 720 can include a number of cryptographically linked blocks.In the example of FIG. 7B, a block 722 includes an example data record724 describing a digital loan transaction. The data record 724 includesvarious information describing the digital loan transaction including,for example, a transaction identifier, transaction details, a borrower,a lender, a principal amount associated with the digital loan, a countof tokens loaned, terms associated with the loan (e.g., interest rate,repayment terms, etc.), and a maturity date, to name some examples. Manyvariations are possible.

FIG. 7C illustrates another diagram of the example blockchain 720. Inthe example of FIG. 7C, a block 732 includes an example data record 734describing a payment transaction made based on tokens associated with adigital loan. For example, the data record 734 can reflect a paymentmade from a borrower to a payee. The data record 734 includes variousinformation describing the payment transaction including, for example, atransaction identifier, transaction details, a payor, a payee, and acount of tokens paid, to name some examples. Many variations arepossible.

FIG. 7D illustrates yet another diagram of the example blockchain 720.In the example of FIG. 7D, a block 742 includes an example data record744 describing a loan payment transaction for a digital loan. Forexample, the data record 744 can reflect a payment made from a borrowerto a lender, such as a principal and/or interest payment. The datarecord 744 includes various information describing the paymenttransaction including, for example, a transaction identifier,transaction details, a payor, a payee, and a number of tokens paid, toname some examples. Many variations are possible.

FIG. 7E illustrates an example diagram 750 for generating a digital loanreport, in accordance with various embodiments of the presenttechnology. In the example of FIG. 7E, a blockchain associated with ablockchain network 752 can be queried 754. The blockchain network 752can comprise nodes associated with a blockchain-based digital loanpayment network. A set of digital loan transactions 756 responsive tothe query 754 can be obtained. The set of digital loan transactions 756can describe various transactions that occurred between participants inthe blockchain-based digital loan payment network. A digital loan report758 can be generated based on the set of digital loan transactions 756.The digital loan report 758 can detail transactions that occurredbetween participants in the blockchain-based digital loan paymentnetwork, as described above. For example, the digital loan report 758can identify network participants that received, sent, or redeemedpayment loan tokens minted for circulation in the blockchain-baseddigital loan payment network. Many variations are possible.

Hardware Implementation

The techniques described herein are implemented by one or morespecial-purpose computing devices. The special-purpose computing devicesmay be hard-wired to perform the techniques, or may include circuitry ordigital electronic devices such as one or more application-specificintegrated circuits (ASICs) or field programmable gate arrays (FPGAs)that are persistently programmed to perform the techniques, or mayinclude one or more hardware processors programmed to perform thetechniques pursuant to program instructions in firmware, memory, otherstorage, or a combination. Such special-purpose computing devices mayalso combine custom hard-wired logic, ASICs, or FPGAs with customprogramming to accomplish the techniques. The special-purpose computingdevices may be desktop computer systems, server computer systems,portable computer systems, handheld devices, networking devices or anyother device or combination of devices that incorporate hard-wiredand/or program logic to implement the techniques.

Computing device(s) are generally controlled and coordinated byoperating system software, such as iOS, Android, Chrome OS, Windows XP,Windows Vista, Windows 7, Windows 8, Windows Server, Windows CE, Unix,Linux, SunOS, Solaris, iOS, Blackberry OS, VxWorks, or other compatibleoperating systems. In other embodiments, the computing device may becontrolled by a proprietary operating system. Conventional operatingsystems control and schedule computer processes for execution, performmemory management, provide file system, networking, I/O services, andprovide a user interface functionality, such as a graphical userinterface (“GUI”), among other things.

FIG. 8 is a block diagram that illustrates a computer system 800 uponwhich any of the embodiments described herein may be implemented. Thecomputer system 800 includes a bus 802 or other communication mechanismfor communicating information, one or more hardware processors 804coupled with bus 802 for processing information. Hardware processor(s)804 may be, for example, one or more general purpose microprocessors.

The computer system 800 also includes a main memory 806, such as arandom access memory (RAM), cache and/or other dynamic storage devices,coupled to bus 802 for storing information and instructions to beexecuted by processor 804. Main memory 806 also may be used for storingtemporary variables or other intermediate information during executionof instructions to be executed by processor 804. Such instructions, whenstored in storage media accessible to processor 804, render computersystem 800 into a special-purpose machine that is customized to performthe operations specified in the instructions.

The computer system 800 further includes a read only memory (ROM) 808 orother static storage device coupled to bus 802 for storing staticinformation and instructions for processor 804. A storage device 810,such as a magnetic disk, optical disk, or USB thumb drive (Flash drive),etc., is provided and coupled to bus 802 for storing information andinstructions.

The computer system 800 may be coupled via bus 802 to a display 812,such as a cathode ray tube (CRT) or LCD display (or touch screen), fordisplaying information to a computer user. An input device 814,including alphanumeric and other keys, is coupled to bus 802 forcommunicating information and command selections to processor 804.Another type of user input device is cursor control 816, such as amouse, a trackball, or cursor direction keys for communicating directioninformation and command selections to processor 804 and for controllingcursor movement on display 812. This input device typically has twodegrees of freedom in two axes, a first axis (e.g., x) and a second axis(e.g., y), that allows the device to specify positions in a plane. Insome embodiments, the same direction information and command selectionsas cursor control may be implemented via receiving touches on a touchscreen without a cursor.

The computing system 800 may include a user interface module toimplement a GUI that may be stored in a mass storage device asexecutable software codes that are executed by the computing device(s).This and other modules may include, by way of example, components, suchas software components, object-oriented software components, classcomponents and task components, processes, functions, attributes,procedures, subroutines, segments of program code, drivers, firmware,microcode, circuitry, data, databases, data structures, tables, arrays,and variables.

In general, the word “module,” as used herein, refers to logic embodiedin hardware or firmware, or to a collection of software instructions,possibly having entry and exit points, written in a programminglanguage, such as, for example, Java, C or C++. A software module may becompiled and linked into an executable program, installed in a dynamiclink library, or may be written in an interpreted programming languagesuch as, for example, BASIC, Perl, Python, or GoLang. It will beappreciated that software modules may be callable from other modules orfrom themselves, and/or may be invoked in response to detected events orinterrupts. Software modules configured for execution on computingdevices may be provided on a computer readable medium, such as a compactdisc, digital video disc, flash drive, magnetic disc, or any othertangible medium, or as a digital download (and may be originally storedin a compressed or installable format that requires installation,decompression or decryption prior to execution). Such software code maybe stored, partially or fully, on a memory device of the executingcomputing device, for execution by the computing device. Softwareinstructions may be embedded in firmware, such as an EPROM. It will befurther appreciated that hardware modules may be comprised of connectedlogic units, such as gates and flip-flops, and/or may be comprised ofprogrammable units, such as programmable gate arrays or processors. Themodules or computing device functionality described herein arepreferably implemented as software modules, but may be represented inhardware or firmware. Generally, the modules described herein refer tological modules that may be combined with other modules or divided intosub-modules despite their physical organization or storage.

The computer system 800 may implement the techniques described hereinusing customized hard-wired logic, one or more ASICs or FPGAs, firmwareand/or program logic which in combination with the computer systemcauses or programs computer system 800 to be a special-purpose machine.According to one embodiment, the techniques herein are performed bycomputer system 800 in response to processor(s) 804 executing one ormore sequences of one or more instructions contained in main memory 806.Such instructions may be read into main memory 806 from another storagemedium, such as storage device 810. Execution of the sequences ofinstructions contained in main memory 806 causes processor(s) 804 toperform the process steps described herein. In alternative embodiments,hard-wired circuitry may be used in place of or in combination withsoftware instructions.

The term “non-transitory media,” and similar terms, as used hereinrefers to any media that store data and/or instructions that cause amachine to operate in a specific fashion. Such non-transitory media maycomprise non-volatile media and/or volatile media. Non-volatile mediaincludes, for example, optical or magnetic disks, such as storage device810. Volatile media includes dynamic memory, such as main memory 806.Common forms of non-transitory media include, for example, a floppydisk, a flexible disk, hard disk, solid state drive, magnetic tape, orany other magnetic data storage medium, a CD-ROM, any other optical datastorage medium, any physical medium with patterns of holes, a RAM, aPROM, and EPROM, a FLASH-EPROM, NVRAM, any other memory chip orcartridge, and networked versions of the same.

Non-transitory media is distinct from but may be used in conjunctionwith transmission media. Transmission media participates in transferringinformation between non-transitory media. For example, transmissionmedia includes coaxial cables, copper wire and fiber optics, includingthe wires that comprise bus 802. Transmission media can also take theform of acoustic or light waves, such as those generated duringradio-wave and infra-red data communications.

Various forms of media may be involved in carrying one or more sequencesof one or more instructions to processor 804 for execution. For example,the instructions may initially be carried on a magnetic disk or solidstate drive of a remote computer. The remote computer can load theinstructions into its dynamic memory and send the instructions over atelephone line using a modem. A modem local to computer system 800 canreceive the data on the telephone line and use an infra-red transmitterto convert the data to an infra-red signal. An infra-red detector canreceive the data carried in the infra-red signal and appropriatecircuitry can place the data on bus 802. Bus 802 carries the data tomain memory 806, from which processor 804 retrieves and executes theinstructions. The instructions received by main memory 806 may retrievesand executes the instructions. The instructions received by main memory806 may optionally be stored on storage device 810 either before orafter execution by processor 804.

The computer system 800 also includes a communication interface 818coupled to bus 802. Communication interface 818 provides a two-way datacommunication coupling to one or more network links that are connectedto one or more local networks. For example, communication interface 818may be an integrated services digital network (ISDN) card, cable modem,satellite modem, or a modem to provide a data communication connectionto a corresponding type of telephone line. As another example,communication interface 818 may be a local area network (LAN) card toprovide a data communication connection to a compatible LAN (or WANcomponent to communicated with a WAN). Wireless links may also beimplemented. In any such implementation, communication interface 818sends and receives electrical, electromagnetic or optical signals thatcarry digital data streams representing various types of information.

A network link typically provides data communication through one or morenetworks to other data devices. For example, a network link may providea connection through local network to a host computer or to dataequipment operated by an Internet Service Provider (ISP). The ISP inturn provides data communication services through the world wide packetdata communication network now commonly referred to as the “Internet”.Local network and Internet both use electrical, electromagnetic oroptical signals that carry digital data streams. The signals through thevarious networks and the signals on network link and throughcommunication interface 818, which carry the digital data to and fromcomputer system 800, are example forms of transmission media.

The computer system 800 can send messages and receive data, includingprogram code, through the network(s), network link and communicationinterface 818. In the Internet example, a server might transmit arequested code for an application program through the Internet, the ISP,the local network and the communication interface 818.

The received code may be executed by processor 804 as it is received,and/or stored in storage device 810, or other non-volatile storage forlater execution.

Each of the processes, methods, and algorithms described in thepreceding sections may be embodied in, and fully or partially automatedby, code modules executed by one or more computer systems or computerprocessors comprising computer hardware. The processes and algorithmsmay be implemented partially or wholly in application-specificcircuitry.

The various features and processes described above may be usedindependently of one another, or may be combined in various ways. Allpossible combinations and sub-combinations are intended to fall withinthe scope of this disclosure. In addition, certain method or processblocks may be omitted in some implementations. The methods and processesdescribed herein are also not limited to any particular sequence, andthe blocks or states relating thereto can be performed in othersequences that are appropriate. For example, described blocks or statesmay be performed in an order other than that specifically disclosed, ormultiple blocks or states may be combined in a single block or state.The example blocks or states may be performed in serial, in parallel, orin some other manner. Blocks or states may be added to or removed fromthe disclosed example embodiments. The example systems and componentsdescribed herein may be configured differently than described. Forexample, elements may be added to, removed from, or rearranged comparedto the disclosed example embodiments.

Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainembodiments include, while other embodiments do not include, certainfeatures, elements and/or steps. Thus, such conditional language is notgenerally intended to imply that features, elements and/or steps are inany way required for one or more embodiments or that one or moreembodiments necessarily include logic for deciding, with or without userinput or prompting, whether these features, elements and/or steps areincluded or are to be performed in any particular embodiment.

Any process descriptions, elements, or blocks in the flow diagramsdescribed herein and/or depicted in the attached figures should beunderstood as potentially representing modules, segments, or portions ofcode which include one or more executable instructions for implementingspecific logical functions or steps in the process. Alternateimplementations are included within the scope of the embodimentsdescribed herein in which elements or functions may be deleted, executedout of order from that shown or discussed, including substantiallyconcurrently or in reverse order, depending on the functionalityinvolved, as would be understood by those skilled in the art.

It should be emphasized that many variations and modifications may bemade to the above-described embodiments, the elements of which are to beunderstood as being among other acceptable examples. All suchmodifications and variations are intended to be included herein withinthe scope of this disclosure. The foregoing description details certainembodiments of the invention. It will be appreciated, however, that nomatter how detailed the foregoing appears in text, the invention can bepracticed in many ways. As is also stated above, it should be noted thatthe use of particular terminology when describing certain features oraspects of the invention should not be taken to imply that theterminology is being re-defined herein to be restricted to including anyspecific characteristics of the features or aspects of the inventionwith which that terminology is associated. The scope of the inventionshould therefore be construed in accordance with the appended claims andany equivalents thereof.

Language

Throughout this specification, plural instances may implement components(or modules), operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components (or modules) in exampleconfigurations may be implemented as a combined structure or component.Similarly, structures and functionality presented as a single component(or module) may be implemented as separate components (or modules).These and other variations, modifications, additions, and improvementsfall within the scope of the subject matter herein.

Although an overview of the subject matter has been described withreference to specific example embodiments, various modifications andchanges may be made to these embodiments without departing from thebroader scope of embodiments of the present disclosure. Such embodimentsof the subject matter may be referred to herein, individually orcollectively, by the term “invention” merely for convenience and withoutintending to voluntarily limit the scope of this application to anysingle disclosure or concept if more than one is, in fact, disclosed.

The embodiments illustrated herein are described in sufficient detail toenable those skilled in the art to practice the teachings disclosed.Other embodiments may be used and derived therefrom, such thatstructural and logical substitutions and changes may be made withoutdeparting from the scope of this disclosure. The Detailed Description,therefore, is not to be taken in a limiting sense, and the scope ofvarious embodiments is defined only by the appended claims, along withthe full range of equivalents to which such claims are entitled.

It will be appreciated that an “engine,” “system,” “data store,” and/or“database” may comprise software, hardware, firmware, and/or circuitry.In one example, one or more software programs comprising instructionscapable of being executable by a processor may perform one or more ofthe functions of the engines, data stores, databases, or systemsdescribed herein. In another example, circuitry may perform the same orsimilar functions. Alternative embodiments may comprise more, less, orfunctionally equivalent engines, systems, data stores, or databases, andstill be within the scope of present embodiments. For example, thefunctionality of the various systems, engines, data stores, and/ordatabases may be combined or divided differently.

The data stores described herein may be any suitable structure (e.g., anactive database, a relational database, a self-referential database, atable, a matrix, an array, a flat file, a documented-oriented storagesystem, a non-relational No-SQL system, and the like), and may becloud-based or otherwise.

As used herein, the term “or” may be construed in either an inclusive orexclusive sense. Moreover, plural instances may be provided forresources, operations, or structures described herein as a singleinstance. Additionally, boundaries between various resources,operations, engines, engines, and data stores are somewhat arbitrary,and particular operations are illustrated in a context of specificillustrative configurations. Other allocations of functionality areenvisioned and may fall within a scope of various embodiments of thepresent disclosure. In general, structures and functionality presentedas separate resources in the example configurations may be implementedas a combined structure or resource. Similarly, structures andfunctionality presented as a single resource may be implemented asseparate resources. These and other variations, modifications,additions, and improvements fall within a scope of embodiments of thepresent disclosure as represented by the appended claims. Thespecification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense.

Although the invention has been described in detail for the purpose ofillustration based on what is currently considered to be the mostpractical and preferred implementations, it is to be understood thatsuch detail is solely for that purpose and that the invention is notlimited to the disclosed implementations, but, on the contrary, isintended to cover modifications and equivalent arrangements that arewithin the spirit and scope of the appended claims. For example, it isto be understood that the present invention contemplates that, to theextent possible, one or more features of any embodiment can be combinedwith one or more features of any other embodiment.

The invention claimed is:
 1. A computer-implemented method forconducting digital loan payment transactions in a digital loan paymentnetwork of an entity based on a blockchain network, the methodcomprising: minting, by an I-node in the blockchain network, paymentloan tokens to conduct digital loan transactions within the digital loanpayment network, the I-node being managed by the entity andparticipating as a node in the blockchain network of the entity, theI-node including at least one processor and memory, the payment loantokens being pegged to fiat currency or digital currency, and thepayment loan tokens being entity-specific tokens that are circulated inthe digital loan payment network of the entity; determining, by theI-node, a number of payment loan tokens to be provided to a borrowerbased on a digital loan transaction, wherein the borrower is a networkparticipant associated with the digital loan payment network; providing,by the I-node, a payment from a digital wallet associated with theI-node to a digital wallet associated with a U-node in the blockchainnetwork, the U-node is associated with the borrower, the U-nodeincluding at least one processor and memory, and the payment being basedon the number of payment loan tokens to be provided to the borrowerbased on the digital loan transaction, wherein payees that receive oneor more payment loan tokens from the borrower can redeem the one or morepayment loan tokens as fiat or digital currency through the I-node;generating, by the I-node, a data record that represents the digitalloan transaction associated with the payment from the I-node to theU-node; and providing, by the I-node, the data record to a T-node thatparticipates as a node in the blockchain network, wherein the T-Node isone of a plurality of T-Nodes, each of the plurality of T-Nodes beingprovisioned by one of a plurality of banks each of which is a member ofa common bank consortium, wherein the T-node posts the data record to ablockchain associated with the digital loan payment network hosted bythe bank consortium.
 2. The computer-implemented method of claim 1,further comprising: determining, by the I-node, a request from a payeethat received payment loan tokens from the borrower to convert one ormore payment loan tokens to fiat or digital currency; providing, by theI-node, instructions to a computing system associated with a financialinstitution to convert the one or more payment loan tokens to fiat ordigital currency; and causing, by the I-node, the one or more paymentloan tokens to be burned.
 3. The computer-implemented method of claim 2,wherein fiat currency or digital currency that is pegged to the paymentloan tokens is reduced based on the conversion of the one or morepayment loan tokens to fiat or digital currency, and wherein a principalamount associated with the digital loan transaction is reduced based ona payment associated with the principal amount, wherein the payment isbased on fiat currency, digital currency, or payment loan tokens.
 4. Thecomputer-implemented method of claim 1, further comprising: determining,by the I-node, a request from a payee that received payment loan tokensfrom the borrower or a second payee to convert one or more payment loantokens to fiat or digital currency; determining, by the I-node, that acash-out functionality associated with the payment loan tokens has beendisabled; and providing, by the I-node, a notification to the payee orthe second payee in response to the request, wherein the notificationindicates that the request to convert the one or more payment loantokens to fiat or digital currency has been denied.
 5. Thecomputer-implemented method of claim 4, wherein determining that thecash-out functionality associated with the payment loan tokens has beendisabled further comprises: determining, by the I-node, that theborrower has defaulted on one or more loan payments associated with thedigital loan transaction.
 6. The computer-implemented method of claim 5,wherein the cash-out functionality can be disabled to one or more of:(i) prevent redemption of the payment loan tokens possessed by theborrower, (ii) prevent redemption of payment loan tokens associated withthe digital loan transaction that are in circulation within the digitalloan payment network, or (iii) prevent redemption of payment loan tokensassociated with the digital loan that have yet to be repaid.
 7. Thecomputer-implemented method of claim 1, further comprising: minting, bythe I-node in the blockchain network, second payment loan tokens toconduct digital loan transactions, wherein the second payment loantokens are loan-specific tokens that are minted specifically for thedigital loan transaction, wherein the second payment loan tokens arelender-specific tokens that are minted specifically for a lender thatprocesses the digital loan transaction, wherein the second payment loantokens are special purpose tokens that are minted specifically for aspecified special purpose, wherein the second payment loan tokens areindustry-specific tokens that are minted specifically for transactionsbetween entities associated with a particular industry, wherein thesecond payment loan tokens are geography-specific tokens that are mintedspecifically for transactions between entities associated with aparticular geographic region, wherein the second payment loan tokens arecountry-specific tokens that are minted specifically for transactionsbetween entities associated with a particular country, wherein thesecond payment loan tokens are project-specific tokens that are mintedspecifically for transactions between entities associated with aparticular project, or wherein the second payment loan tokens arelender-agnostic tokens that can be used to facilitate transactionsbetween entities regardless of lender.
 8. The computer-implementedmethod of claim 1, further comprising: generating, by the I-node, adigital loan report based on one or more queries to the blockchainassociated with the digital loan payment network, wherein the digitalloan report includes transaction information for the digital loantransaction recorded in the blockchain.
 9. The computer-implementedmethod of claim 1, wherein the digital loan payment network comprises aplurality of nodes including at least one minting node associated with alender that processes the digital loan transaction, at least oneprocessing node associated with the lender, or both.
 10. Thecomputer-implemented method of claim 1, further comprising: determining,by the I-node, that payment loan tokens associated with a digital walletof a payee are inaccessible; determining, by the I-node, a payment loantoken balance for the digital wallet based on the blockchain associatedwith the digital loan payment network; and replacing, by the I-node, thepayment loan tokens that are inaccessible with replacement payment loantokens.
 11. The computer-implemented method of claim 10, whereinreplacing the payment loan tokens that are inaccessible with replacementpayment loan tokens further comprises: restricting, by the I-node, thepayment loan tokens that are inaccessible, wherein the restrictingcomprises: causing, by the I-node, the digital wallet of the payee to belocked; causing, by the I-node, a transfer of the payment loan tokensthat are inaccessible from the digital wallet to a different digitalwallet; and burning, by the I-node, the transferred payment loan tokensfrom the different digital wallet; minting, by the I-node, thereplacement payment loan tokens; and providing, by the I-node, thereplacement payment loan tokens to a replacement digital walletassociated with the payee.
 12. The computer-implemented method of claim1, further comprising: determining, by the I-node, a payment transactionbetween a first payee that received payment loan tokens from theborrower and a second payee; generating, by the I-node, a data recordthat represents the payment transaction, wherein the data record isposted to the blockchain associated with the digital loan paymentnetwork.
 13. The computer-implemented method of claim 12, furthercomprising: determining, by the I-node, a request from the second payeethat received payment loan tokens from the first payee to convert one ormore payment loan tokens to fiat or digital currency; providing, by theI-node, instructions to a computing system associated with a financialinstitution to convert the one or more payment loan tokens to fiat ordigital currency; and causing, by the I-node, the one or more paymentloan tokens to be burned.
 14. The computer-implemented method of claim1, wherein a lender can define a smart contract to control usage of thepayment loan tokens, wherein the smart contract can programmaticallycontrol usage of the payment loan tokens for at least one of: aspecified purpose, payee, or project.
 15. The computer-implementedmethod of claim 1, further comprising: determining, by the I-node, apayment made by the borrower to the entity based on the payment loantokens to satisfy at least a portion of a principal amount associatedwith the digital loan transaction; reducing, by the I-node, an amount offiat currency or digital currency from an escrow account that supportsthe payment loan tokens associated with the digital loan transaction,wherein the amount of fiat currency or digital currency reduced is basedon the payment made by the borrower to the entity; and burning, by theI-node, one or more payment loan tokens associated with the payment. 16.The computer-implemented method of claim 1, further comprising:determining, by the I-node, a payment made by the borrower to the entitybased on fiat currency or digital currency to satisfy at least a portionof a principal amount associated with the digital loan transaction; andreducing, by the I-node, an amount of fiat currency or digital currencyfrom an escrow account that supports the payment loan tokens associatedwith the digital loan transaction, wherein the amount of fiat currencyreduced is based on the payment made by the borrower to the entity. 17.The computer-implemented method of claim 1, further comprising:determining, by the I-node, a payment made by the borrower to the entitybased on the payment loan tokens to satisfy an amount of interestassociated with the digital loan transaction; burning, by the I-node,the payment loan tokens associated with the payment; and generating, bythe I-node, a data record that represents the payment made by theborrower to the entity, wherein the data record is posted to theblockchain associated with the blockchain-based digital loan paymentnetwork.
 18. The computer-implemented method of claim 1, furthercomprising: determining, by the I-node, a payment made by the borrowerto the entity based on fiat currency or digital currency to satisfy anamount of interest associated with the digital loan transaction; andgenerating, by the I-node, a data record that represents the paymentmade by the borrower to the entity, wherein the data record is posted tothe blockchain associated with the blockchain-based digital loan paymentnetwork.
 19. The computer-implemented method of claim 1, wherein thepayment loan tokens associated with the digital loan transaction areassociated with an obligation to pay interest, wherein the obligation topay interest is triggered only after one or more of the payment loantokens are used in a payment to a payee.
 20. An I-node for conductingdigital loan payment transactions in a digital loan payment network ofan entity based on a blockchain network, comprising: at least oneprocessor; and a memory storing instructions that, when executed by theat least one processor, cause the I-node to perform: minting paymentloan tokens to conduct digital loan transactions within the digital loanpayment network, the I-node being managed by the entity andparticipating as a node in the blockchain network of the entity, thepayment loan tokens being pegged to fiat currency or digital currency,and the payment loan tokens being entity-specific tokens that arecirculated in the digital loan payment network of the entity;determining a number of payment loan tokens to be provided to a borrowerbased on a digital loan transaction, wherein the borrower is a networkparticipant associated with the blockchain-based digital loan paymentnetwork; providing a payment from a digital wallet associated with theI-node to a digital wallet associated with a U-node in the blockchainnetwork, the U-node is associated with the borrower, the U-nodeincluding at least one processor and memory, and the payment being basedon the number of payment loan tokens to be provided to the borrowerbased on the digital loan transaction, wherein payees that receive oneor more payment loan tokens from the borrower can redeem the one or morepayment loan tokens as fiat or digital currency through the I-node;generating a data record that represents the digital loan transactionassociated with the payment from the I-node to the U-node; andproviding, by the I-node, the data record to a T-node that participatesas a node in the blockchain network, wherein the T-Node is one of aplurality of T-Nodes, each of the plurality of T-Nodes being provisionedby one of a plurality of banks each of which is a member of a commonbank consortium, wherein the T-node posts the data record to ablockchain associated with the digital loan payment network hosted bythe bank consortium.
 21. The I-node of claim 20, wherein theinstructions further cause the system to perform: determining a requestfrom a payee that received payment loan tokens from the borrower toconvert one or more payment loan tokens to fiat or digital currency;providing instructions to a computing system associated with a financialinstitution to convert the one or more payment loan tokens to fiat ordigital currency; and causing the one or more payment loan tokens to beburned.
 22. The I-node of claim 21, wherein fiat currency or digitalcurrency that is pegged to the payment loan tokens is reduced based onthe conversion of the one or more payment loan tokens to fiat or digitalcurrency, and wherein a principal amount associated with the digitalloan transaction is reduced based on a payment associated with theprincipal amount, wherein the payment is based on fiat currency, digitalcurrency, or payment loan tokens.
 23. The I-node of claim 20, whereinthe instructions further cause the system to perform: determining arequest from a payee that received payment loan tokens from the borroweror a second payee to convert one or more payment loan tokens to fiat ordigital currency; determining that a cash-out functionality associatedwith the payment loan tokens has been disabled; and providing anotification to the payee or the second payee in response to therequest, wherein the notification indicates that the request to convertthe one or more payment loan tokens to fiat or digital currency has beendenied.
 24. The I-node of claim 23, wherein determining that thecash-out functionality associated with the payment loan tokens has beendisabled further causes the system to perform determining that theborrower has defaulted on one or more loan payments associated with thedigital loan transaction.
 25. A non-transitory computer-readable storagemedium including instructions for conducting digital loan paymenttransactions in a digital loan payment network of an entity based on ablockchain network, wherein the instructions, when executed by at leastone processor of an I-node, cause the I-node to perform: minting paymentloan tokens to conduct digital loan transactions within the digital loanpayment network, the I-node being managed by the entity andparticipating as a node in the blockchain network of the entity, thepayment loan tokens being pegged to fiat currency or digital currency,and the payment loan tokens being entity-specific tokens that arecirculated in the digital loan payment network of the entity;determining a number of payment loan tokens to be provided to a borrowerbased on a digital loan transaction, wherein the borrower is a networkparticipant associated with the blockchain-based digital loan paymentnetwork; providing a payment from a digital wallet associated with theI-node to a digital wallet associated with a U-node in the blockchainnetwork, the U-node is associated with the borrower, the U-nodeincluding at least one processor and memory, and the payment being basedon the number of payment loan tokens to be provided to the borrowerbased on the digital loan transaction, wherein payees that receive oneor more payment loan tokens from the borrower can redeem the one or morepayment loan tokens as fiat or digital currency through the I-node;generating a data record that represents the digital loan transactionassociated with the payment from the I-node to the U-node; andproviding, by the I-node, the data record to a T-node that participatesas a node in the blockchain network, wherein the T-Node is one of aplurality of T-Nodes, each of the plurality of T-Nodes being provisionedby one of a plurality of banks each of which is a member of a commonbank consortium, wherein the T-node posts the data record to ablockchain associated with the digital loan payment network hosted bythe bank consortium.
 26. The non-transitory computer-readable storagemedium of claim 25, wherein the instructions further cause the I-node toperform: determining a request from a payee that received payment loantokens from the borrower to convert one or more payment loan tokens tofiat or digital currency; providing instructions to a computing systemassociated with a financial institution to convert the one or morepayment loan tokens to fiat or digital currency; and causing the one ormore payment loan tokens to be burned.
 27. The non-transitorycomputer-readable storage medium of claim 26, wherein fiat currency ordigital currency that is pegged to the payment loan tokens is reducedbased on the conversion of the one or more payment loan tokens to fiator digital currency, and wherein a principal amount associated with thedigital loan transaction is reduced based on a payment associated withthe principal amount, wherein the payment is based on fiat currency,digital currency, or payment loan tokens.
 28. The non-transitorycomputer-readable storage medium of claim 25, wherein the instructionsfurther cause the I-node to perform: determining a request from a payeethat received payment loan tokens from the borrower or a second payee toconvert one or more payment loan tokens to fiat or digital currency;determining that a cash-out functionality associated with the paymentloan tokens has been disabled; and providing a notification to the payeeor the second payee in response to the request, wherein the notificationindicates that the request to convert the one or more payment loantokens to fiat or digital currency has been denied.
 29. Thenon-transitory computer-readable storage medium of claim 28, whereindetermining that the cash-out functionality associated with the paymentloan tokens has been disabled further causes the I-node to perform:determining that the borrower has defaulted on one or more loan paymentsassociated with the digital loan transaction.